SOAP Node (DSmart)

Make SOAP web service requests with authentication for DSmart services

Actions17

SetPaymentCancel

AI-generated

Overview

This node enables interaction with a SOAP web service specifically designed for DSmart payment and banking operations. It supports various SOAP operations including setting payment cancellations, retrieving invoices, managing direct debits, and more. The node is useful in scenarios where you need to automate or integrate financial transaction management, such as canceling payments, querying invoice details, or handling direct debit agreements via SOAP APIs.

For the SetPaymentCancel operation, the node sends a request to cancel a payment by providing necessary identifiers like bank code, subscriber number, invoice number, and cancellation date. This is beneficial for automating payment cancellation workflows in financial systems that use the DSmart SOAP API.

Example use cases:

  • Automatically cancel a payment when a refund is issued.
  • Integrate payment cancellation into a larger billing automation workflow.
  • Synchronize payment status updates between external systems and your internal databases.

Properties

Name Meaning
SOAP Service URL The URL of the SOAP web service endpoint to which requests are sent. Default is http://dstahsilat.dsmart.com.tr/DsmartOnlinePaymentSystem.asmx?WSDL.
Input Mode Choose how to send the SOAP request: either by specifying parameters (Parameters) or by providing a full custom SOAP envelope XML (Custom SOAP Envelope).
Parameters A collection of input parameters used when Input Mode is set to Parameters. Includes:
- Extra Variables: Custom name-value pairs to be injected into the SOAP template.
- Invoice ID (string)
- Opbel (number)
- TCKN (string)
- Vkont (string)
- Year (number, default current year)
Authentication Source How authentication credentials are provided: either using stored credentials (Use Credentials) or manual input (Manual Input).
Authentication When Authentication Source is Manual Input, specify username and password here for SOAP API authentication.
SOAP Envelope When Input Mode is Custom SOAP Envelope, provide the complete SOAP XML envelope here. Supports variable placeholders like {{username}}, {{password}}, and n8n expressions such as {{ $json.field }}.

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 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.
  • statusCode: HTTP status code if available.
  • statusText: HTTP status text if available.
  • rawResponse: Raw response data if available.

The node does not output binary data.

Dependencies

  • Requires access to the DSmart SOAP web service endpoint.
  • Needs valid authentication credentials (either stored or manually entered) for the SOAP API.
  • Uses the axios library for HTTP requests.
  • Uses the xml2js library to parse XML SOAP responses.
  • No special environment variables are required beyond standard n8n credential configuration.

Troubleshooting

  • Common issues:

    • Incorrect SOAP Service URL or network connectivity problems can cause request failures.
    • Invalid or missing authentication credentials will result in authorization errors.
    • Malformed SOAP envelopes or incorrect parameter values may cause the SOAP service to return faults.
    • 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.
    • SOAP Faults: Inspect the rawResponse for detailed SOAP fault messages; verify that all required parameters are correctly set.
    • Network errors or timeouts: Ensure the SOAP service URL is reachable and responsive.

  • Resolution tips:

    • Use the "Custom SOAP Envelope" mode to craft and test exact SOAP requests if parameter mode fails.
    • Enable "Continue On Fail" to capture error details without stopping the workflow.
    • Verify date formats and required fields match the SOAP API specification.

Links and References

Discussion