DSmart SOAP Node

Make SOAP web service requests with authentication for DSmart services

Actions17

Overview

This node enables making authenticated SOAP web service requests specifically for DSmart services. It is designed to interact with various SOAP operations provided by the DSmart payment and direct debit system, such as retrieving canceled direct debit lists, bank agreements, invoices, payments, and more.

A common use case is automating financial data retrieval or updates from the DSmart platform within an n8n workflow. For example, you can fetch a list of canceled direct debits for reconciliation purposes or confirm bank agreement dates automatically.

The node allows flexible authentication either by using stored credentials or manual input, and supports fully customizable SOAP envelopes with dynamic variable substitution, enabling integration with diverse SOAP operations.

Properties

Name Meaning
SOAP Service URL The URL endpoint of the SOAP web service to which requests are sent. Default points to the DSmart online payment system WSDL.
Authentication Source Method to provide authentication credentials: either "Use Credentials" (from stored API credentials) or "Manual Input" (enter username and password manually).
Authentication When "Manual Input" is selected, this collection holds the username and password for SOAP authentication.
SOAP Envelope The full SOAP envelope XML string to send in the request body. Supports placeholders like {{username}}, {{password}}, and other variables that get replaced dynamically at runtime. This allows customizing the SOAP action payload per operation.

For the GetCanceledDirectDebitList operation, the default SOAP envelope includes these key variables:

  • username and password: Authentication credentials.
  • bankCode: Bank identifier (defaulted internally to "24").
  • agreementDate: Optional date filter for agreements.
  • domainName: Domain context, e.g., "emlakbank.com.tr".
  • Optional repeated username and password fields inside the body.

Output

The node outputs JSON data structured as follows:

  • response: Parsed JSON object extracted from the SOAP response's main result element corresponding to the invoked operation.
  • rawResponse: The raw XML SOAP response as a string.
  • statusCode: HTTP status code returned by the SOAP service.
  • statusText: HTTP status text message.

Each output item corresponds to one input item processed, preserving pairing.

No binary data output is produced by this node.

Dependencies

  • Requires access to the DSmart SOAP web service endpoint.
  • Needs valid authentication credentials (username and password) either via stored credentials or manual entry.
  • Uses the following npm packages bundled with the node:
    • axios for HTTP POST requests.
    • xml2js for parsing XML SOAP responses into JSON.

No additional environment variables or n8n-specific configurations are required beyond credential setup.

Troubleshooting

  • Authentication errors: If the SOAP service returns authentication failures, verify that the username and password are correct and correspond to valid DSmart API credentials.
  • Timeouts: The node uses a 30-second timeout for requests; slow network or service issues may cause timeouts. Consider increasing timeout if needed.
  • Malformed SOAP envelope: Ensure the SOAP envelope XML is well-formed and all required placeholders are correctly set. Invalid XML will cause parsing or request errors.
  • Unexpected response structure: If the SOAP response format changes or differs, the node might fail to extract the expected result. Review the rawResponse output for debugging.
  • Continue on Fail: Enable this option to allow workflows to continue processing subsequent items even if some requests fail.

Links and References

Discussion