Actions6
Overview
This node integrates with the Swan.io API to perform various banking-related operations. Specifically, the "Mutation - InitiateCreditTransfers" operation allows users to initiate one or multiple credit transfers from a specified account. This is useful in scenarios where automated payments or batch transfers need to be executed programmatically, such as payroll disbursements, vendor payments, or sending money to multiple beneficiaries.
For example, a business could use this node to automate monthly salary payments by specifying each employee's bank details and payment amount, triggering all transfers in one workflow execution.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the type of access token used for authentication: "User Access Token" or "Project Access Token". For initiating credit transfers, "User Access Token" must be selected. |
| Account ID | The unique identifier of the bank account from which the credit transfers will be initiated. |
| Consent Redirect URL | A URL to which the user will be redirected after granting consent for the credit transfers. |
| Credit Transfers | A collection of one or more credit transfer entries, each containing: |
| - Amount: The monetary value to transfer (string). | |
| - Currency: The currency code for the amount (default is "EUR"). | |
| - Beneficiary IBAN: The International Bank Account Number of the beneficiary. | |
| - Beneficiary Name: The name of the beneficiary receiving the funds. | |
| - Label: A label describing the transfer. | |
| - Reference: A reference string for the transfer, often used for bookkeeping or identification. |
Output
The node outputs JSON data representing the response from the Swan API after initiating the credit transfers. This typically includes details about the initiated transfers, such as their status, identifiers, and any relevant metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token of type "User Access Token" configured in n8n credentials.
- The node depends on the Swan.io API being accessible and properly authenticated.
- The "Consent Redirect URL" must be a valid URL that the user can be redirected to after granting consent.
Troubleshooting
- Authentication Errors: If the wrong authentication type is selected (e.g., "Project Access Token" instead of "User Access Token"), the node will throw an error indicating that a user token is required.
- Missing Required Fields: Omitting required fields like Account ID, Consent Redirect URL, or any required credit transfer details will cause the node to fail.
- Invalid IBAN or Currency: Providing incorrectly formatted IBANs or unsupported currency codes may result in API errors.
- Consent Issues: The consent redirect URL must be correctly set up to handle user redirection; otherwise, the consent flow may fail.
- API Request Failures: Network issues or invalid API credentials will cause request failures. Check connectivity and credential validity.
Links and References
- Swan.io API Documentation (for detailed API usage and parameters)
- IBAN Format Reference (to validate beneficiary IBANs)
- n8n Documentation (for general guidance on using credentials and nodes)