SOAP Node (DSmart)

Make SOAP web service requests with authentication for DSmart services

Actions17

GetDirectDebitToInvoiceByDueDate

AI-generated

Overview

This node enables interaction with a SOAP web service specifically designed for DSmart services, allowing users to perform various operations related to banking and payment processing. The operation GetDirectDebitToInvoiceByDueDate retrieves direct debit information linked to invoices filtered by a due date.

Typical use cases include:

  • Fetching direct debit transactions associated with invoices that are due on a specific date.
  • Integrating with financial systems to automate reconciliation or reporting of direct debit payments.
  • Automating workflows that require up-to-date invoice payment status via direct debit.

For example, a user can configure this node to query all direct debit entries for invoices due on a certain date, enabling automated follow-up actions such as sending reminders or updating accounting records.

Properties

Name Meaning
SOAP Service URL The URL endpoint of the SOAP web service to which requests will be sent. Default is http://dstahsilat.dsmart.com.tr/DsmartOnlinePaymentSystem.asmx?WSDL.
Input Mode Choose how to send the request: either by specifying parameters individually (Parameters) or by providing a complete custom SOAP envelope XML (Custom SOAP Envelope).
Parameters A collection of input parameters used when Input Mode is set to Parameters. Includes:
- Extra Variables: Custom name-value pairs to be injected into the SOAP envelope.
- Invoice ID (string)
- Opbel (number)
- TCKN (string)
- Vkont (string)
- Year (number, default 2025)
Authentication Source How authentication credentials are provided: either using stored credentials (Use Credentials) or manual entry (Manual Input).
Authentication When Authentication Source is Manual Input, specify username and password here for SOAP API authentication.
SOAP Envelope When Input Mode is Custom SOAP Envelope, provide the full SOAP XML envelope here. Supports variable placeholders like {{username}}, {{password}}, and n8n expressions.

Output

The node outputs an array of items where each item contains:

  • json.response: The parsed SOAP response object corresponding to the requested operation's result.
  • json.rawResponse: The raw XML string returned from the SOAP service.
  • json.statusCode: HTTP status code of the SOAP response.
  • json.statusText: HTTP status text of the SOAP response.

The structure inside response depends on the SOAP operation but generally contains the data returned by the GetDirectDebitToInvoiceByDueDate SOAP method, such as direct debit details filtered by due date.

No binary data output is produced by this node.

Dependencies

  • Requires access to the specified SOAP web service URL.
  • Needs valid authentication credentials for the SOAP API, either via stored credentials or manual input.
  • Uses the axios library for HTTP requests.
  • Uses the xml2js library to parse XML SOAP responses into JSON objects.

Troubleshooting

  • Authentication errors: If the SOAP service returns authentication failures, verify that the username and password are correct and properly supplied either via credentials or manual input.
  • Timeouts: The node sets a 30-second timeout for requests; if the service is slow or unresponsive, consider network issues or increasing timeout settings if possible.
  • Malformed SOAP envelope: When using custom envelopes, ensure the XML is well-formed and all required variables are correctly replaced.
  • Parsing errors: If the SOAP response format changes or is unexpected, parsing may fail or return incomplete data. Check the raw response in output for debugging.
  • HTTP errors: Non-200 HTTP responses will be included in the output error object if "Continue On Fail" is enabled; otherwise, they will throw an error stopping execution.

Links and References

Discussion