SOAP Node (DSmart)

Make SOAP web service requests with authentication for DSmart services

Actions17

ConfirmGetBankAgreementDate

AI-generated

Overview

This node enables making authenticated SOAP web service requests specifically for DSmart services. It supports various operations related to bank agreements, direct debits, invoices, payments, and cancellations by sending SOAP envelopes to a specified SOAP service URL.

The node is useful in scenarios where you need to integrate with DSmart's SOAP-based APIs to retrieve or update financial and banking information programmatically. For example, you can confirm bank agreement dates, get invoice details, set payment information, or fetch lists of direct debit agreements.

Practical examples:

  • Confirming the date of a bank agreement before processing transactions.
  • Retrieving detailed invoice information for billing automation.
  • Setting or canceling direct debit instructions based on customer requests.
  • Fetching payment cancellation details for reconciliation purposes.

Properties

Name Meaning
SOAP Service URL The URL endpoint of the SOAP web service to which requests are sent.
Input Mode Choose how to send the SOAP request: either by specifying parameters that will be injected into a predefined SOAP envelope template ("Parameters") or by providing a fully custom SOAP XML envelope ("Custom SOAP Envelope").
Parameters A collection of input parameters used when "Parameters" mode is selected. Includes fields like Invoice ID, Opbel (operation number), TCKN (Turkish ID number), Vkont (contract number), Year, and extra template variables.
Authentication Source How authentication credentials are provided: either using stored API credentials or manual input of username and password.
Authentication Username and password for manual authentication input. Only shown if manual authentication is selected.
SOAP Envelope The full SOAP XML envelope to send when "Custom SOAP Envelope" mode is selected. Supports variable placeholders (e.g., {{username}}) and n8n expressions for dynamic content injection.

Output

The node outputs an array of JSON objects, each representing the response from the SOAP service for each input item processed. Each output object contains:

  • response: The parsed SOAP response body as a JSON object, focusing on the specific operation result.
  • 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 an error field with the error message and any available HTTP response details.

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 for storing API keys or usernames/passwords.

Troubleshooting

  • Common issues:

    • Incorrect SOAP Service URL or network connectivity problems may cause request failures.
    • Invalid or missing authentication credentials will lead to authorization errors.
    • Malformed custom SOAP envelopes can cause parsing or server errors.
    • 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.
    • HTTP 404 Not Found: Verify the SOAP service URL is correct.
    • XML parsing errors: Ensure the SOAP response is well-formed XML; if using custom envelopes, verify their correctness.
    • Timeout errors: Increase timeout settings or check network stability.

To resolve errors, verify all inputs, especially authentication and SOAP envelope structure, and consult the SOAP service documentation for required parameters.

Links and References

Discussion