SOAP Node (DSmart)

Make SOAP web service requests with authentication for DSmart services

Actions17

PaymentAllListDetail

AI-generated

Overview

This node enables interaction with a SOAP web service specifically designed for DSmart payment and banking services. It allows users to perform various operations such as retrieving payment details, bank agreements, direct debit information, invoices, and managing payments or cancellations by sending properly formatted SOAP requests.

A common use case is automating financial data retrieval or updates from the DSmart system within an n8n workflow, such as fetching detailed payment lists, confirming bank agreement dates, or setting payment information programmatically.

For example, using the PaymentAllListDetail operation, a user can retrieve comprehensive payment details filtered by parameters like bank code and agreement date, which is useful for reconciliation or reporting tasks.

Properties

Name Meaning
SOAP Service URL The endpoint URL of the SOAP web service to which requests are sent. Default is http://dstahsilat.dsmart.com.tr/DsmartOnlinePaymentSystem.asmx?WSDL.
Input Mode Select how to send the SOAP request: either by specifying individual parameters (Parameters) or by providing a fully 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 values.
Authentication Source Choose how authentication credentials are provided: either by using stored credentials (Use Credentials) or by manual input (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}}, {{password}}, and N8N expressions for dynamic content injection.

Output

The node outputs JSON data containing:

  • response: The parsed SOAP response body relevant to the requested operation.
  • rawResponse: The raw XML response string received from the SOAP service.
  • statusCode: HTTP status code of the SOAP response.
  • statusText: HTTP status text of the SOAP response.

Each output item corresponds to one input item processed, preserving pairing.

No binary data output is produced by this node.

Dependencies

  • Requires access to the specified SOAP web service URL.
  • 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 XML SOAP responses into JSON.

Troubleshooting

  • Authentication errors: If the SOAP service returns authentication failures, verify that the correct username and password are provided either through credentials or manual input.
  • Timeouts: Requests have a 30-second timeout; slow network or service issues may cause timeouts.
  • Invalid SOAP envelope: When using custom envelopes, ensure the XML is well-formed and all required placeholders are correctly replaced.
  • Parsing errors: If the SOAP response structure changes or is unexpected, parsing might fail or return incomplete data. Check the raw response for troubleshooting.
  • HTTP errors: Non-200 HTTP responses will be included in the output error object if "Continue On Fail" is enabled; otherwise, they throw exceptions.

Links and References

Discussion