Actions37
- Contact Actions
- Invoice Actions
- Item Actions
- Payment Actions
- Estimate Actions
- Tax Actions
- Bank Account Actions
Overview
This node integrates with the Alegra API to manage bank accounts, specifically enabling the transfer of funds between two bank accounts. The "Transfer" operation allows users to specify a source account, a destination account, an amount, and a date for the transfer. Optional fields such as description and observations can also be added to provide additional context.
Common scenarios where this node is beneficial include automating internal fund transfers within an organization, reconciling accounts, or scheduling future transfers. For example, a business could automate monthly transfers from a revenue account to a savings account, including notes about the purpose of the transfer.
Properties
| Name | Meaning |
|---|---|
| Source Account Name or ID | The bank account to transfer funds from. Choose from a list of available accounts or specify an ID using an expression. |
| Destination Account Name or ID | The bank account to transfer funds to. Choose from a list of available accounts or specify an ID using an expression. |
| Amount | The amount of money to transfer. Supports decimal values with two digits precision. |
| Date | The date when the transfer should occur, formatted as YYYY-MM-DD. |
| Additional Fields | Optional extra information about the transfer: |
| - Description | A text description of the transfer. |
| - Observations | Additional observations or notes related to the transfer. |
Output
The output JSON contains the response from the Alegra API after performing the transfer. This typically includes details of the created transfer record such as:
id_destination: The ID of the destination account.amount: The transferred amount.date: The date of the transfer.description(if provided): Description of the transfer.observations(if provided): Additional notes.
No binary data is output by this node.
Dependencies
- Requires an active connection to the Alegra API via an API key credential configured in n8n.
- The node uses the Alegra API endpoint
/bank-accounts/{sourceAccount}/transferto perform the transfer. - The environment URL for the Alegra API must be set in the credential configuration.
Troubleshooting
- Invalid Account IDs: If the source or destination account IDs are incorrect or do not exist, the API will return an error. Verify that the accounts exist and are correctly selected or specified.
- Insufficient Funds: The API may reject the transfer if the source account does not have sufficient balance.
- Date Format Errors: Ensure the date is provided in the correct format (YYYY-MM-DD). Incorrect formats may cause request failures.
- Authentication Errors: If the API key credential is missing or invalid, requests will fail. Confirm the API key is correctly configured.
- Network Issues: Connectivity problems can cause timeouts or failed requests. Check network access to Alegra's API endpoints.
Error messages returned by the node will generally reflect the underlying API errors. Reviewing the message content helps identify the root cause.
Links and References
- Alegra API Documentation (official API docs)
- n8n Expressions Documentation (for specifying dynamic input values)