Actions17
- BankAgreementList
- CancelAllListDetail
- ConfirmGetBankAgreementDate
- GetBankAgreement
- GetCanceledDirectDebitList
- GetDirectDebitAgreement
- GetDirectDebitInfo
- GetDirectDebitList
- GetDirectDebitToInvoiceByDueDate
- GetInvoice
- GetPaymentCancel
- PaymentAllListDetail
- ReturnLink
- SetDirectDebit
- SetDirectDebitCancel
- SetPayment
- SetPaymentCancel
GetDirectDebitList
AI-generatedOverview
This node enables interaction with DSmart SOAP web services by sending authenticated SOAP requests and receiving structured responses. It supports multiple predefined operations related to banking and direct debit management, such as retrieving direct debit lists, bank agreements, invoices, payment cancellations, and more.
The node is useful in scenarios where you need to integrate DSmart's SOAP-based financial services into your workflows, automating tasks like fetching direct debit information, managing payments, or querying invoice details.
For example, you can use this node to:
- Retrieve a list of direct debits for a specific bank and date.
- Query invoice information for a subscriber.
- Cancel a payment or direct debit agreement.
- Send custom SOAP envelopes for advanced or unsupported operations.
Properties
| Name | Meaning |
|---|---|
| SOAP Service URL | The URL endpoint of the SOAP web service 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 parameters (parameters) or by providing a complete custom SOAP envelope XML (envelope). |
| Parameters | When using parameters input mode, a collection of fields to specify operation parameters, including: - Extra Variables: Custom name-value pairs to be used as template variables in the SOAP envelope. - Invoice ID (string) - Opbel (number) - TCKN (string) - Vkont (string) - Year (number, default current year) |
| Authentication Source | How to provide authentication credentials: - Use Credentials: Uses stored API credentials. - Manual Input: Enter username and password manually. |
| Authentication | When using manual authentication, enter: - Username: Authentication username. - Password: Authentication password. |
| SOAP Envelope | When using envelope input mode, provide the full SOAP envelope XML. Supports template variables like {{username}}, {{password}}, and other placeholders that will be replaced dynamically. |
Output
The node outputs an array of items, each containing:
json.response: The parsed SOAP response body relevant to the executed operation, typically an object representing the result data.json.rawResponse: The raw XML string returned from 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:
json.error: Error message.json.statusCode: HTTP status code if available.json.statusText: HTTP status text if available.json.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 (either stored credentials or manual username/password).
- Uses the
axioslibrary for HTTP requests. - Uses the
xml2jslibrary to parse XML SOAP responses. - No special environment variables required beyond standard n8n credential configuration.
Troubleshooting
- Authentication errors: Ensure correct username and password are provided either via credentials or manual input. Incorrect credentials will cause authentication failures.
- Timeouts: The node uses a 30-second timeout for requests. If the SOAP service is slow or unresponsive, consider network issues or increasing timeout if possible.
- Invalid SOAP envelope: When using custom SOAP envelopes, ensure the XML is well-formed and all required placeholders are correctly set; otherwise, the service may reject the request.
- Parsing errors: If the SOAP response structure changes or is unexpected, parsing might fail or return incomplete data. Verify the SOAP response format matches expectations.
- HTTP errors: Check the HTTP status codes and messages in the output for clues on failures (e.g., 404 Not Found, 500 Internal Server Error).