SOAP Node (DSmart)

Make SOAP web service requests with authentication for DSmart services

Actions17

GetInvoice

AI-generated

Overview

This node enables interaction with DSmart SOAP web services by sending authenticated SOAP requests and retrieving responses. It supports multiple operations related to banking and invoice management, such as fetching invoice information, bank agreements, direct debit details, payment cancellations, and more.

The node is useful in scenarios where you need to integrate DSmart's SOAP-based financial or billing services into your workflows, automating data retrieval or updates without manual intervention. For example, you can automatically fetch invoice details for a subscriber or confirm bank agreement dates as part of a larger automation process.

Specifically, the GetInvoice operation retrieves detailed invoice information from the SOAP service, which can be used for billing reconciliation, customer notifications, or financial reporting.

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.
Input Mode Selects how the SOAP request is constructed: either by providing individual parameters (Parameters) or by supplying a full custom SOAP envelope XML (Custom SOAP Envelope).
Parameters A collection of input fields used when Input Mode is set to Parameters. Includes:
- Extra Variables: Custom name-value pairs to inject into the SOAP template.
- Invoice ID (string)
- Opbel (number)
- TCKN (string)
- Vkont (string)
- Year (number, default current year)
Authentication Source Defines how authentication credentials are provided: either using stored API credentials (Use Credentials) or manual entry (Manual Input).
Authentication When manual authentication is selected, this collection holds the username and password for SOAP service authentication.
SOAP Envelope When Input Mode is Custom SOAP Envelope, this multiline string contains the full SOAP XML envelope. Supports variable placeholders like {{username}}, N8N expressions, and credential field references.

Output

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

  • response: The parsed SOAP response body relevant to the requested operation, extracted from the SOAP envelope.
  • rawResponse: The raw XML response string received from 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 will contain an error object with:

  • 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 (username and password), either via stored credentials or manual input.
  • Uses the axios library for HTTP requests.
  • Uses the xml2js library to parse XML SOAP responses.
  • No additional environment variables are required beyond standard n8n credential configuration.

Troubleshooting

  • Authentication errors: Ensure that the correct username and password are provided, either through credentials or manual input. Incorrect credentials will cause authentication failures.
  • Timeouts: The node sets a 30-second timeout for SOAP requests. If the service is slow or unresponsive, consider network issues or increasing timeout settings externally.
  • Malformed SOAP envelope: When using the custom SOAP envelope mode, ensure the XML is well-formed and all required placeholders are correctly replaced; otherwise, the SOAP service may reject the request.
  • Parsing errors: If the SOAP response structure changes or is unexpected, the node might fail to extract the result properly. Verify the SOAP response format matches expectations.
  • HTTP errors: Check the statusCode and statusText in the output for clues on HTTP-level issues (e.g., 404 Not Found, 500 Internal Server Error).

Links and References

Discussion