SOAP Node (DSmart)

Make SOAP web service requests with authentication for DSmart services

Actions17

SetPayment

AI-generated

Overview

This node enables making authenticated SOAP web service requests specifically for DSmart services. It supports various operations related to banking and payment systems, such as setting payments, retrieving invoices, managing direct debits, and more. The node can send requests either by specifying parameters or by providing a fully custom SOAP envelope.

Common scenarios include:

  • Automating payment processing by sending payment details to the SOAP API.
  • Retrieving bank agreements or invoice information from the DSmart system.
  • Managing direct debit agreements and cancellations.
  • Querying payment cancellation status or obtaining return links.

For example, using the SetPayment operation, you can automate submitting payment information including bank code, subscriber number, invoice number, payment amount, and date, which is useful in financial workflows integrating with DSmart's payment system.

Properties

Name Meaning
SOAP Service URL The URL of the SOAP web service endpoint to which requests are sent. Default points to the DSmart online payment system WSDL.
Input Mode Choose how to send the SOAP request: either by specifying individual parameters ("Parameters") or by providing a complete custom SOAP XML envelope ("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 substitution.
Authentication Source How to provide authentication credentials: either use stored credentials ("Use Credentials") or enter username and password manually ("Manual Input").
Authentication When manual authentication is selected, specify Username and Password here.
SOAP Envelope When "Input Mode" is "Custom SOAP Envelope", provide the full SOAP XML envelope here. Supports variable placeholders like {{username}}, N8N expressions, and credential field references.

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 requested 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, either via stored credentials or manual input.
  • 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: Ensure correct username and password are provided either via credentials or manual input. Incorrect credentials will cause SOAP faults or HTTP 401 errors.
  • Timeouts: The node uses a 30-second timeout for requests. Long-running SOAP calls may fail if they exceed this limit.
  • Malformed SOAP envelope: When using custom envelopes, ensure the XML is well-formed and all required placeholders are correctly replaced.
  • Invalid operation name: Selecting an unsupported operation or mismatching the SOAPAction header may result in errors.
  • Parsing errors: If the SOAP response structure changes or is unexpected, parsing might fail or return incomplete data.

To resolve issues, verify the SOAP service URL, credentials, and input parameters. Use the raw response output to debug SOAP faults.

Links and References

Discussion