SOAP Node (DSmart)

Make SOAP web service requests with authentication for DSmart services

Actions17

BankAgreementList

AI-generated

Overview

This node enables making authenticated SOAP web service requests specifically for DSmart services. It supports multiple predefined SOAP operations related to banking agreements, direct debits, payments, invoices, and cancellations. Users can either provide parameters that the node will inject into predefined SOAP envelopes or supply a fully custom SOAP envelope XML.

Common scenarios include:

  • Retrieving lists of bank agreements or canceled direct debits.
  • Querying invoice or payment information.
  • Setting or canceling direct debits and payments.
  • Confirming agreement dates or obtaining return links.

Practical example: A finance team could automate fetching bank agreement lists or invoice details from the DSmart system to integrate with their accounting workflows.

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 request: either by providing parameters that fill a predefined SOAP envelope ("Parameters") or by supplying a complete custom SOAP envelope XML ("Custom SOAP Envelope").
Parameters When using "Parameters" mode, this collection allows setting various input values such as Invoice ID, Year, TCKN (Turkish ID number), Opbel (operation code), Vkont (account number), and extra template variables.
Authentication Source Select how authentication credentials are provided: either use stored API credentials ("Use Credentials") or enter username and password manually ("Manual Input").
Authentication If manual authentication is selected, specify the username and password here.
SOAP Envelope When using "Custom SOAP Envelope" mode, enter the full SOAP XML envelope here. Supports variable placeholders like {{username}}, N8N expressions, and credential field references. This property is shown only for the BankAgreementList operation in envelope mode.

Output

The node outputs an array of JSON objects, each corresponding to one input item processed. Each output object contains:

  • response: The parsed SOAP response body content relevant to the invoked operation.
  • 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 the SOAP response includes nested elements named after the operation suffixed with "Response" and "Result", those are extracted and presented under response for easier consumption.

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: Ensure correct username and password are provided, either via credentials or manual input. Check if the SOAP service requires additional headers or specific auth types.
  • Timeouts or network errors: Verify the SOAP service URL is reachable and responsive. Network issues or incorrect URLs can cause failures.
  • Malformed SOAP envelope: When using custom envelopes, ensure the XML is well-formed and all required placeholders are correctly replaced.
  • Unexpected response structure: If the SOAP response does not contain expected elements, verify the operation name matches the SOAPAction header and the envelope body.
  • Continue on fail: If enabled, the node will output error details per item instead of stopping execution.

Links and References

Discussion