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 allowing you to update existing bank account details. It is useful in scenarios where you need to programmatically modify bank account information such as the account name, description, bank name, account number, or status within your Alegra accounting system.
Practical examples include:
- Automatically updating bank account details when changes occur in your financial systems.
- Synchronizing bank account information from other platforms into Alegra.
- Activating or deactivating bank accounts based on business rules or workflows.
Properties
| Name | Meaning |
|---|---|
| Bank Account ID | The unique identifier of the bank account you want to update. |
| Update Fields | A collection of fields to update on the bank account. Options include: |
| - Name | The new name for the bank account. |
| - Description | A textual description of the bank account. |
| - Bank Name | The name of the bank where the account is held. |
| - Account Number | The bank account number. |
| - Status | Whether the bank account is active (true) or inactive (false). |
Output
The node outputs JSON data representing the updated bank account object returned by the Alegra API after a successful update operation. This typically includes all current properties of the bank account, reflecting the changes made.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Alegra API.
- The node uses the Alegra API endpoint configured via the credential's environment URL.
- Proper network access to Alegra's API endpoints is necessary.
Troubleshooting
Common Issues:
- Invalid or missing Bank Account ID will cause the update to fail.
- Providing invalid field values (e.g., incorrect data types) in update fields may result in API errors.
- Network connectivity issues can prevent communication with Alegra API.
- Insufficient permissions or expired API credentials will cause authentication failures.
Error Messages and Resolutions:
- "Unknown error occurred": General catch-all; check network connection and API credentials.
- API errors indicating "not found" usually mean the Bank Account ID does not exist.
- Validation errors from the API indicate incorrect or malformed input fields; verify the data types and required fields.
- Authentication errors suggest invalid or missing API key; ensure the credential is correctly set up in n8n.
Links and References
- Alegra API Documentation (official resource for API endpoints and data models)
- n8n Documentation (for general usage of custom nodes and credentials)