DSmart SOAP Node

Make SOAP web service requests with authentication for DSmart services

Actions17

Overview

This node enables making authenticated SOAP web service requests specifically tailored for DSmart services. It allows users to send custom SOAP envelopes to a specified SOAP service URL, supporting dynamic insertion of credentials and other variables into the XML payload.

A common use case is integrating with DSmart's payment and banking-related SOAP APIs to retrieve or submit data such as return links, bank agreements, direct debit information, invoices, payments, and cancellations.

For example, using the "ReturnLink" operation, you can request a return link from the DSmart SOAP service by sending a properly formatted SOAP envelope with authentication details embedded. This is useful in workflows that require interaction with DSmart's online payment system.

Properties

Name Meaning
SOAP Service URL The endpoint URL of the SOAP web service to which the request will be sent. Example: http://dstahsilat.dsmart.com.tr/DsmartOnlinePaymentSystem.asmx?WSDL.
Authentication Source How to provide authentication credentials: either "Use Credentials" (from stored API credentials) or "Manual Input" (enter username and password manually).
Authentication When "Manual Input" is selected, this collection lets you specify the Username and Password for authentication.
SOAP Envelope The full SOAP envelope XML string to send in the request body. Supports variable placeholders like {{username}}, n8n expressions such as {{ $json.field }}, and direct credential access. For the "ReturnLink" operation, it defaults to a minimal envelope requesting the return link.

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 response 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.
  • statusCode, statusText, rawResponse: If available, details from the failed HTTP response.

The node does not output binary data.

Dependencies

  • Requires access to the DSmart SOAP web service endpoint.
  • Needs valid authentication credentials (username and password), either provided via stored credentials or manual input.
  • Uses the axios library for HTTP requests.
  • Uses the xml2js library to parse XML responses.

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/403 errors.
  • Timeouts: The node sets a 30-second timeout for requests. Long-running SOAP calls may fail if they exceed this limit.
  • Malformed SOAP envelope: The SOAP envelope must be well-formed XML and include all required elements for the chosen operation. Invalid XML or missing placeholders can cause parsing or server errors.
  • Incorrect SOAPAction header: The SOAPAction HTTP header is set based on the operation name. Using an unsupported operation or mismatched SOAPAction may result in server errors.
  • Parsing errors: If the SOAP response structure changes or is unexpected, the node might fail to extract the expected response part. Review the rawResponse output for debugging.

Links and References

Discussion