DSmart SOAP Node

Make SOAP web service requests with authentication for DSmart services

Actions17

Overview

This node enables making SOAP web service requests specifically tailored for DSmart services, with support for authentication. It allows users to send custom SOAP envelopes to a specified SOAP service URL and receive parsed responses. The node is useful in scenarios where integration with DSmart's SOAP APIs is required, such as retrieving bank agreement details, canceling lists, confirming agreements, managing direct debits, payments, invoices, and related financial operations.

For example, the "CancelAllListDetail" operation can be used to fetch detailed information about all canceled items associated with a bank code and other parameters, which is helpful for financial reconciliation or auditing purposes.

Properties

Name Meaning
SOAP Service URL The URL of the SOAP web service endpoint to which the request will be sent.
Authentication Source How to provide authentication credentials: either by using stored API credentials or by manual input of username and password.
Authentication When manual input is selected, this collection allows entering the username and password for SOAP API authentication.
SOAP Envelope The complete SOAP envelope XML to send in the request body. Supports variable placeholders like {{username}}, N8N expressions (e.g., {{ $json.field }}), and direct credential field access. This XML defines the SOAP operation and its parameters.

Output

The node outputs an array of JSON objects, each corresponding to an input item processed. Each output object contains:

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

If an error occurs and the node is configured to continue on failure, the output includes:

  • error: Error message describing what went wrong.
  • statusCode: HTTP status code if available.
  • statusText: HTTP status text if available.
  • rawResponse: Raw response data if available.

The node does not output binary data.

Dependencies

  • Requires an active internet connection to reach the specified SOAP service URL.
  • Uses an HTTP client library to send POST requests with SOAP XML payloads.
  • Parses XML responses using an XML-to-JavaScript object parser.
  • Requires either:
    • An API key credential (username and password) configured in n8n credentials, or
    • Manual entry of username and password for authentication.

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 the SOAP service to reject the request.
    • Timeout errors if the SOAP service is slow or unresponsive.

  • Error messages:

    • Errors include HTTP status codes and messages from the SOAP service.
    • If the node fails and is not set to continue on fail, it throws an error indicating the item index and error details.
    • To resolve errors, verify the SOAP URL, credentials, and SOAP envelope correctness. Also, ensure that required variables are properly provided and formatted.

Links and References

Discussion