SOAP Node (DSmart)Install

Overview

This node enables interaction with a SOAP web service specifically designed for DSmart payment and direct debit services. It allows users to perform various operations such as retrieving direct debit information, bank agreements, invoices, payment cancellations, and more by sending properly formatted SOAP requests.

For the GetDirectDebitInfo operation, the node fetches detailed information about direct debit arrangements associated with a subscriber number and bank code. This is useful in scenarios where you need to verify or retrieve direct debit details for financial reconciliation, customer account management, or automated payment processing.

Practical example:
A finance team can use this node to automatically pull direct debit info for a subscriber to check their payment status or update records in an ERP system without manual intervention.

Properties

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 data returned by the SOAP service.
• json.rawResponse: The raw XML string of the entire SOAP response.
• json.statusCode: HTTP status code of the SOAP request.
• json.statusText: HTTP status text of the SOAP request.

The output structure is consistent regardless of the operation, allowing downstream nodes to handle the parsed data easily.

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 objects.
• No additional environment variables are required beyond standard n8n credential configuration.

Troubleshooting

• Common issues:

  • Incorrect SOAP Service URL or network connectivity problems may cause request failures.
  • Invalid or missing authentication credentials will result in authorization errors.
  • Malformed custom SOAP envelopes can lead to SOAP faults or parsing errors.
  • Timeout errors if the SOAP service is slow or unresponsive.

• Error messages:

  • Errors from the SOAP service are captured and included in the output under json.error.
  • HTTP error codes and messages are also included in the output for easier diagnosis.
  • If "Continue On Fail" is disabled, the node throws an error stopping execution on failure.

• Resolution tips:

  • Verify the SOAP service URL and ensure it is reachable.
  • Double-check authentication credentials.
  • Use the "Parameters" input mode initially to avoid XML syntax errors.
  • Increase timeout settings if necessary (currently set to 30 seconds).
  • Inspect raw SOAP responses (rawResponse) for detailed fault information.

Links and References

• SOAP Web Services Introduction
• Axios HTTP Client
• xml2js XML to JSON Parser
• n8n Documentation on Credentials