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 tailored for DSmart services. It allows users to send custom SOAP envelopes to a specified SOAP service URL, supporting various operations related to banking agreements, direct debits, payments, invoices, and cancellations.

A common use case is integrating with DSmart's online payment system to retrieve or confirm bank agreement dates, get invoice information, manage direct debit agreements, or handle payment cancellations programmatically within an n8n workflow.

For example, the "ConfirmGetBankAgreementDate" operation can be used to verify the date of a bank agreement by sending relevant bank code and authentication details in a SOAP request, then processing the response for further automation steps.

Properties

Name Meaning
SOAP Service URL The URL endpoint of the SOAP web service to which the request will be sent.
Authentication Source Method to provide authentication credentials: either using stored API credentials or manual input of username and password.
Authentication When manual input is selected, this collection holds the username and password for authenticating the SOAP request.
SOAP Envelope The full SOAP envelope XML string that defines the SOAP request body and header. Supports variable placeholders like {{username}}, {{password}}, N8N expressions (e.g., {{ $json.field }}), and direct credential access. This property changes depending on the selected operation; for "ConfirmGetBankAgreementDate", it includes fields such as bankCode, agreementDate, domainName, username, and password.

Output

The node outputs JSON data containing:

  • response: The parsed SOAP response body relevant to the invoked operation, extracted from the SOAP envelope.
  • rawResponse: The raw XML response string received from the SOAP service.
  • statusCode: HTTP status code of the SOAP request.
  • statusText: HTTP status text message.

If the SOAP request fails and "Continue On Fail" is enabled, the output JSON will include:

  • error: Error message describing the failure.
  • statusCode, statusText, rawResponse: Corresponding HTTP error details 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 (generic SOAP API credentials) configured in n8n for authentication, or
    • Manual entry of username and password for SOAP authentication.
  • Uses the axios library for HTTP requests.
  • Uses the xml2js library to parse XML SOAP responses into JSON.

Troubleshooting

  • Common issues:

    • Incorrect SOAP Service URL or network connectivity problems may cause request failures.
    • Invalid or missing authentication credentials will result in authentication errors.
    • Malformed SOAP envelope XML or incorrect variable placeholders can cause SOAP faults.
    • Timeout errors if the SOAP service does not respond within 30 seconds.

  • Error messages:

    • Authentication failures typically return HTTP 401 or 403 status codes; verify credentials.
    • SOAP fault responses may appear in the rawResponse field; check the SOAP envelope structure.
    • Network errors or DNS resolution failures indicate connectivity issues.

  • Resolution tips:

    • Double-check the SOAP Service URL and ensure it is accessible.
    • Verify credentials are correct and properly mapped in the node.
    • Validate the SOAP envelope XML syntax and placeholder variables.
    • Increase timeout settings if necessary (currently fixed at 30 seconds).
    • Enable "Continue On Fail" to capture error details without stopping the workflow.

Links and References

Discussion