DSmart SOAP Node

Overview

This node enables making authenticated SOAP web service requests specifically tailored for DSmart services. It allows users to call various SOAP operations by sending custom SOAP envelopes with dynamic data, including authentication credentials and other parameters.

A common use case is integrating with DSmart's financial or payment systems to retrieve or manage direct debit lists, bank agreements, invoices, payments, and cancellations. For example, the "GetDirectDebitList" operation fetches a list of direct debit records filtered by bank code, agreement date, and domain name.

This node is beneficial when you need to automate interactions with DSmart SOAP APIs within n8n workflows, such as fetching financial data regularly or triggering payment-related actions programmatically.

Properties

For the GetDirectDebitList operation specifically, the default SOAP envelope includes these variables:

• username: Authentication username.
• password: Authentication password.
• bankCode: Bank identifier (defaulted to "24").
• agreementDate: Date filter for agreements (optional).
• domainName: Domain name related to the request (defaulted to "emlakbank.com.tr").
• Additional optional fields like userName and password repeated inside the body.

Output

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

• response: The 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.

If an error occurs and "Continue On Fail" is enabled, the output item will contain:

• error: Error message string.
• statusCode: HTTP status code if available.
• statusText: HTTP status text if available.
• rawResponse: Raw response data if available.

No binary data output is produced by this node.

Dependencies

• Requires an active internet connection to reach the specified SOAP service URL.
• Needs either:
  • An API key credential containing username and password for authentication, or
  • Manual entry of username and password.
• Uses the axios library for HTTP requests.
• Uses the xml2js library to parse XML SOAP responses into JSON.
• No additional environment variables are required beyond standard n8n credential management.

Troubleshooting

• Authentication errors: If the SOAP service returns authentication failures, verify that the username and password are correct and properly injected into the SOAP envelope.
• Timeouts: The node uses a 30-second timeout; slow network or service issues may cause timeouts. Increase timeout in the source code if needed.
• Malformed SOAP envelope: Ensure the SOAP envelope XML is well-formed and all required variables are correctly replaced. Invalid XML will cause parsing errors.
• Incorrect SOAPAction header: The SOAPAction header is dynamically set based on the operation name. If the operation name does not match the service's expected action, the request may fail.
• Parsing errors: If the SOAP response structure changes or is unexpected, the XML parser might fail or return incomplete data. Check the rawResponse output for debugging.
• Empty or missing response elements: Some SOAP responses may omit expected elements; the node attempts to extract the main result but fallback behavior may vary.

Links and References

• SOAP 1.2 Specification
• Axios HTTP Client
• xml2js XML to JS Object Parser
• DSmart SOAP API documentation (if available from your service provider)