SOAP Node (DSmart)

Make SOAP web service requests with authentication for DSmart services

CancelAllListDetail

AI-generated

Overview

This node enables making authenticated SOAP web service requests specifically tailored for DSmart services. It supports multiple predefined SOAP operations related to banking and payment systems, such as retrieving bank agreements, canceling lists, getting invoice information, and setting payments.

The node is useful in scenarios where you need to integrate with DSmart's SOAP-based APIs to automate financial or billing workflows, such as:

  • Fetching detailed cancellation lists for payments.
  • Retrieving invoice or direct debit information.
  • Setting or canceling payments and direct debits.
  • Confirming bank agreement dates.

For the CancelAllListDetail operation, the node sends a request to retrieve details about all canceled items in a list, which can be used for reconciliation or auditing purposes.

Properties

Name Meaning
SOAP Service URL The URL of the SOAP web service endpoint 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 that get injected into a predefined SOAP envelope template ("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 (operation number), TCKN (Turkish ID number), Vkont (contract number), Year, and extra variables.
Authentication Source How to provide authentication credentials: either use stored API credentials or enter username and password manually.
Authentication When manual authentication is selected, specify the 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 other dynamic expressions.

Specific parameters relevant for CancelAllListDetail operation (when using Parameters mode):

  • Extra Variables: Custom key-value pairs to inject into the SOAP envelope.
  • Invoice ID: Identifier for an invoice.
  • Opbel: Numeric operation identifier.
  • TCKN: Turkish national identification number.
  • Vkont: Contract number.
  • Year: Year value, defaulting to 2025.

Output

The node outputs JSON data containing:

  • response: The parsed SOAP response body 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.

The output is paired with the input item index for traceability.

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 credentials or manual input).
  • Uses the axios library for HTTP requests.
  • Uses the xml2js library to parse XML SOAP responses.

Troubleshooting

  • Authentication errors: If the SOAP service returns authentication failures, verify that the username and password are correct and properly provided either via credentials or manual input.
  • Timeouts: Requests have a 30-second timeout; if the service is slow or unresponsive, consider increasing timeout or checking network connectivity.
  • Invalid SOAP envelope: When using custom envelopes, ensure the XML is well-formed and all required placeholders are correctly replaced.
  • Parsing errors: If the response cannot be parsed, check if the SOAP service returned a valid SOAP envelope or an error message.
  • HTTP errors: Non-200 HTTP responses will be included in the output; inspect statusCode and statusText for clues.

If the node is set to continue on failure, errors will be returned in the output JSON instead of stopping execution.

Links and References

Discussion