SOAP Node (DSmart)

Make SOAP web service requests with authentication for DSmart services

Actions17

GetDirectDebitAgreement

AI-generated

Overview

This node enables interaction with a SOAP web service specifically designed for DSmart payment and banking services. It facilitates sending authenticated SOAP requests to perform various operations related to direct debit agreements, bank agreements, invoices, payments, cancellations, and more.

The node supports two input modes:

  • Parameters mode: where you provide operation-specific parameters that the node uses to build the SOAP request.
  • Custom SOAP Envelope mode: where you supply a complete custom SOAP XML envelope, allowing advanced users to craft any request manually.

Typical use cases include:

  • Retrieving direct debit agreement details from a bank.
  • Querying invoice or payment information.
  • Managing direct debit setups or cancellations.
  • Accessing lists of bank agreements or canceled direct debits.

For example, using the "GetDirectDebitAgreement" operation, you can fetch detailed information about direct debit agreements by providing relevant parameters such as bank code and agreement date.

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 converts into a SOAP envelope) or by providing a full custom SOAP envelope XML. Options: Parameters, Custom SOAP Envelope.
Parameters A collection of input parameters used when Input Mode is set to Parameters. Includes:
- Extra Variables: user-defined name-value pairs for template substitution.
- Invoice ID (string)
- Opbel (number)
- TCKN (string)
- Vkont (string)
- Year (number, default current year).
Authentication Source How authentication credentials are provided: either via stored credentials (Use Credentials) or manual input (Manual Input).
Authentication When manual input is selected, specify username and password here for SOAP API authentication.
SOAP Envelope When Input Mode is Custom SOAP Envelope, enter the full SOAP XML envelope here. Supports variable placeholders like {{username}}, {{password}}, N8N expressions, and credential field references.

Output

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

  • response: The parsed SOAP response body content specific 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 "Continue On Fail" is enabled, the output includes:

  • error: Error message describing what went wrong.
  • statusCode, statusText, rawResponse: If available, details from the failed HTTP response.

The node does not output binary data.

Dependencies

  • Requires access to the specified SOAP web service URL.
  • Needs valid authentication credentials (username and password) for the SOAP API, either provided manually or via stored credentials.
  • 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

  • Authentication errors: If the SOAP service returns authentication failures, verify that the username and password are correct and properly supplied either via credentials or manual input.
  • Timeouts or network errors: The node sets a 30-second timeout for requests. Network issues or incorrect service URLs may cause timeouts or connection errors.
  • Malformed SOAP envelopes: When using custom SOAP envelopes, ensure the XML is well-formed and all required fields are correctly templated.
  • Parsing errors: If the SOAP response structure changes or is unexpected, the node might fail to extract the result properly. Check the raw response in output for debugging.
  • Missing parameters: When using parameter mode, ensure all required parameters for the chosen operation are provided; otherwise, the SOAP request may be invalid.

Common error messages will include HTTP status codes and messages from the SOAP service, which should guide corrective actions.

Links and References

This summary focuses on the "GetDirectDebitAgreement" operation of the DSmart SOAP Node as requested.

Discussion