Actions17
- BankAgreementList
- CancelAllListDetail
- ConfirmGetBankAgreementDate
- GetBankAgreement
- GetCanceledDirectDebitList
- GetDirectDebitAgreement
- GetDirectDebitInfo
- GetDirectDebitList
- GetDirectDebitToInvoiceByDueDate
- GetInvoice
- GetPaymentCancel
- PaymentAllListDetail
- ReturnLink
- SetDirectDebit
- SetDirectDebitCancel
- SetPayment
- SetPaymentCancel
SetDirectDebitCancel
AI-generatedOverview
The node enables interaction with a SOAP web service specifically designed for DSmart payment and direct debit services. It supports multiple operations related to bank agreements, direct debit management, invoice retrieval, payment setting and cancellation, and more. The node can send requests either by specifying parameters or by providing a custom SOAP envelope.
This node is beneficial in scenarios where you need to automate financial workflows involving direct debit cancellations, payment processing, or querying banking agreements through SOAP APIs. For example, it can be used to cancel a direct debit authorization for a subscriber, retrieve invoice details, or confirm bank agreement dates programmatically within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| SOAP Service URL | The URL of the SOAP web service endpoint to which requests are sent. Default is http://dstahsilat.dsmart.com.tr/DsmartOnlinePaymentSystem.asmx?WSDL. |
| Operation | The 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: either by specifying individual parameters ("Parameters") or by providing a complete custom SOAP envelope XML ("Custom SOAP Envelope"). |
| Parameters (paramSet) | When using "Parameters" input mode, this collection allows adding specific parameters such as Invoice ID, Opbel (number), TCKN (string), Vkont (string), Year (number), and extra template variables (name-value pairs). |
| Authentication Source | How to provide authentication credentials: either use stored API credentials ("Use Credentials") or enter username and password manually ("Manual Input"). |
| Authentication | When manual input is selected, specify Username and Password for SOAP API authentication. |
| SOAP Envelope | When using "Custom SOAP Envelope" input mode, provide the full SOAP XML envelope here. Supports variable placeholders like {{username}}, {{password}}, N8N expressions, and credential fields. |
Output
The node outputs JSON data containing:
response: The parsed SOAP response body relevant to the executed operation.rawResponse: The raw XML response string 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 includes:
error: Error message.statusCode,statusText,rawResponse: Details from the failed HTTP response if available.
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
axioslibrary for HTTP requests. - Uses the
xml2jslibrary to parse XML SOAP responses. - No additional environment variables are required beyond standard n8n credential configuration.
Troubleshooting
Common issues:
- Incorrect SOAP service URL or network connectivity problems will cause request failures.
- Invalid or missing authentication credentials will result in authentication errors.
- Malformed custom SOAP envelopes may cause parsing or server errors.
- Using parameter names that do not match expected SOAP variables can lead to unexpected results or empty responses.
Error messages:
- HTTP 401 Unauthorized: Check that the username and password are correct and properly provided.
- Timeout errors: Increase timeout settings or check network stability.
- XML parsing errors: Verify that the SOAP response is well-formed XML; also ensure the SOAP envelope template is correctly structured.
- NodeOperationError with context item index: Indicates failure on a specific input item; review input data for that item.