SOAP Node (DSmart)

Make SOAP web service requests with authentication for DSmart services

Actions17

GetBankAgreement

AI-generated

Overview

This node enables interaction with DSmart SOAP web services by sending authenticated SOAP requests and receiving structured responses. It is designed to facilitate various banking-related operations such as retrieving bank agreements, direct debit information, payment details, and invoice data through SOAP API calls.

Common scenarios where this node is beneficial include:

  • Automating retrieval of bank agreement details for financial reconciliation.
  • Querying direct debit or payment cancellation lists for accounting purposes.
  • Integrating invoice and payment status checks into workflows.
  • Sending custom SOAP envelopes for advanced or less common operations supported by the DSmart SOAP API.

For example, a user can configure the node to fetch bank agreement details by providing necessary parameters or a custom SOAP envelope, then use the response data downstream in their automation workflow.

Properties

Name Meaning
SOAP Service URL The URL endpoint of the DSmart SOAP web service to which requests are sent. Default is http://dstahsilat.dsmart.com.tr/DsmartOnlinePaymentSystem.asmx?WSDL.
Operation The specific SOAP operation to execute. Options include: BankAgreementList, CancelAllListDetail, ConfirmGetBankAgreementDate, GetBankAgreement, GetCanceledDirectDebitList, GetDirectDebitAgreement, GetDirectDebitInfo, GetDirectDebitList, GetDirectDebitToInvoiceByDueDate, GetInvoice, GetPaymentCancel, PaymentAllListDetail, ReturnLink, SetDirectDebit, SetDirectDebitCancel, SetPayment, SetPaymentCancel.
Input Mode Choose how to send the request payload: either via structured parameters ("Parameters") or by providing a full custom SOAP envelope XML ("Custom SOAP Envelope").
Parameters When using "Parameters" input mode, a collection of fields to specify operation inputs, including: Invoice ID, Opbel (number), TCKN (string), Vkont (string), Year (number), and Extra Variables (custom name-value pairs).
Authentication Source How authentication credentials are provided: either from stored credentials ("Use Credentials") or manual input ("Manual Input").
Authentication When manual input is selected, username and password fields for SOAP API authentication.
SOAP Envelope When using "Custom SOAP Envelope" input mode, the complete SOAP XML envelope to send. Supports variable placeholders like {{username}}, N8N expressions, and credential field references.

Output

The node outputs an array of items, each containing:

  • json.response: The parsed SOAP response body relevant to the requested operation, typically an object representing the result data.
  • json.rawResponse: The raw XML string returned by the SOAP service.
  • json.statusCode: HTTP status code of the SOAP response.
  • json.statusText: HTTP status text of the SOAP response.

If an error occurs and "Continue On Fail" is enabled, the output item will contain an error message along with any available HTTP status and raw response data.

No binary data output is produced by this node.

Dependencies

  • Requires access to the DSmart SOAP web service endpoint.
  • Needs valid authentication credentials (username and password) 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 for the SOAP API credentials.

Troubleshooting

  • Authentication errors: If the SOAP service returns authentication failures, verify that the correct username and password are provided either via credentials or manual input.
  • Timeouts or network errors: The node uses a 30-second timeout; ensure the SOAP service URL is reachable and responsive.
  • Malformed SOAP envelope: When using custom SOAP envelopes, ensure the XML is well-formed and all required placeholders are correctly replaced.
  • Unexpected response structure: The node attempts to extract the SOAP body and operation-specific result; if the SOAP response format changes, parsing may fail or return unexpected data.
  • Error messages: Errors include HTTP status codes and raw response data to help diagnose issues. Use these details to check service availability or request correctness.

Links and References

Discussion