SOAP Node (DSmart)

Make SOAP web service requests with authentication for DSmart services

SetDirectDebit

AI-generated

Overview

This node enables interaction with a SOAP web service specifically designed for DSmart payment and direct debit services. It supports various operations such as setting direct debits, retrieving bank agreements, invoices, payment cancellations, and more by sending properly formatted SOAP requests.

A common use case is automating financial workflows involving direct debit management or payment processing through the DSmart system. For example, you can programmatically set up a direct debit for a subscriber, retrieve invoice details, or cancel payments without manual intervention.

The node supports two input modes:

  • Parameters: where you provide operation-specific parameters that are injected into predefined SOAP templates.
  • Custom SOAP Envelope: where you supply a fully custom SOAP XML envelope, allowing advanced users to craft specific requests beyond the predefined templates.

Properties

Name Meaning
SOAP Service URL The URL of the SOAP web service endpoint to which requests will be sent. Default points to the DSmart online payment system WSDL.
Operation The SOAP operation to execute. Options include various DSmart service actions like SetDirectDebit, GetInvoice, SetPayment, etc.
Input Mode Choose how to send the request: either by providing individual parameters (Parameters) or by supplying a full custom SOAP envelope XML (Custom SOAP Envelope).
Parameters A collection of input parameters used when Input Mode is set to Parameters. Includes fields like Invoice ID, Opbel (number), TCKN (string), Vkont (string), Year (number), and extra template variables for dynamic substitution. Only shown if Parameters mode is selected.
Authentication Source How to provide authentication credentials: either using stored API credentials (Use Credentials) or entering username and password manually (Manual Input).
Authentication Username and password for manual authentication input. Only visible if Authentication Source is set to Manual Input.
SOAP Envelope The complete SOAP envelope XML to send when Input Mode is Custom SOAP Envelope. Supports variable placeholders like {{username}}, n8n expressions like {{ $json.field }}, and direct credential access. Shown only in envelope mode.

Output

The node outputs JSON data containing:

  • response: The parsed SOAP response body relevant to the executed operation. This is typically an object representing the result data extracted from the SOAP XML.
  • rawResponse: The raw SOAP XML response as a string.
  • statusCode: HTTP status code returned by the SOAP service.
  • statusText: HTTP status text corresponding to the status code.

The output is paired with the input item index to maintain data consistency.

No binary data output is produced by this node.

Dependencies

  • Requires access to the DSmart SOAP web service endpoint.
  • Needs valid authentication credentials either via stored API credentials or manual username/password input.
  • Uses the axios library for HTTP requests.
  • Uses the xml2js library to parse SOAP XML responses.
  • No special environment variables are required beyond standard n8n credential configuration for the SOAP API key.

Troubleshooting

  • Common issues:

    • Incorrect SOAP Service URL or network connectivity problems may cause request failures.
    • Invalid or missing authentication credentials will lead to authorization errors.
    • Malformed custom SOAP envelopes can cause parsing or server errors.
    • Timeout errors if the SOAP service does not respond within 30 seconds.
  • Error messages:

    • Errors from the SOAP service are captured and included in the output JSON under error.
    • HTTP error codes and messages are also provided to help diagnose issues.
    • If continueOnFail is disabled, the node throws an error stopping execution on failure.
  • Resolution tips:

    • Verify the SOAP endpoint URL and network access.
    • Ensure correct credentials are provided.
    • Validate custom SOAP envelopes against the service's WSDL.
    • Use the raw response output to inspect SOAP faults or error details.

Links and References

Discussion