SOAP Node (DSmart)

Make SOAP web service requests with authentication for DSmart services

GetCanceledDirectDebitList

AI-generated

Overview

This node enables making authenticated SOAP web service requests specifically for DSmart services. It supports multiple operations related to banking and payment systems, such as retrieving canceled direct debit lists, bank agreements, invoices, payment cancellations, and more.

For the GetCanceledDirectDebitList operation, the node fetches a list of canceled direct debit transactions from the SOAP service. This is useful in financial workflows where you need to track or audit canceled direct debits for reconciliation or reporting purposes.

Practical examples:

  • Automatically retrieve canceled direct debit records daily to update your accounting system.
  • Integrate with a banking system to monitor canceled payments and trigger alerts or follow-up actions.
  • Use in customer service automation to quickly access canceled direct debit information when handling inquiries.

Properties

Name Meaning
SOAP Service URL The URL endpoint of the SOAP web service to which requests are sent. Default is the DSmart online payment system WSDL URL.
Input Mode Choose how to send the SOAP request: either by specifying parameters (which the node will inject into a predefined SOAP envelope template) or by providing a fully custom SOAP envelope XML. Options: Parameters, Custom SOAP Envelope.
Parameters A collection of input parameters used when "Parameters" mode is selected. Includes fields like Invoice ID, Opbel (number), TCKN (string), Vkont (string), Year (number), and extra template variables for dynamic substitution.
Authentication Source How authentication credentials are provided: either using stored credentials or manual input. Options: Use Credentials, Manual Input.
Authentication When manual input is selected, specify Username and Password here for SOAP API authentication.
SOAP Envelope When "Custom SOAP Envelope" input mode is selected, provide the full SOAP XML envelope here. Supports variable placeholders like {{username}}, {{password}}, and other parameters for dynamic content injection.

Output

The node outputs JSON data containing:

  • response: The parsed SOAP response body relevant to the requested operation, typically an object representing the result data.
  • 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.

This structured output allows downstream nodes to easily consume and process the SOAP response data.

The node does not output binary data.

Dependencies

  • Requires access to the specified SOAP web service URL.
  • Needs valid authentication credentials (either via stored credentials or manual input) to authenticate SOAP requests.
  • Uses the axios library for HTTP requests.
  • Uses the xml2js library to parse XML SOAP responses into JSON.

No special environment variables are required beyond standard n8n credential management.

Troubleshooting

  • Common issues:

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

    • HTTP 401 Unauthorized: Check that the username and password are correct and properly configured.
    • XML parsing errors: Verify that the SOAP response is well-formed XML; also check your custom envelope syntax if used.
    • Timeout errors: Increase timeout settings or verify network stability.
  • Resolution tips:

    • Use the default SOAP envelopes and parameter mode initially to ensure basic connectivity.
    • Validate all input parameters and credentials before execution.
    • Enable "Continue On Fail" in the node settings to handle intermittent failures gracefully.

Links and References


Note: This summary focuses on the GetCanceledDirectDebitList operation within the DSmart SOAP Node as requested.

Discussion