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, the Create Bank Account operation allows users to add a new bank account record in Alegra by specifying details such as the account name, type, initial balance, and other optional fields.
Common scenarios where this node is beneficial include:
- Automating the setup of new bank accounts in Alegra when onboarding clients or setting up financial records.
- Integrating with other systems to synchronize bank account data automatically.
- Streamlining bookkeeping workflows by programmatically managing bank accounts.
For example, a user could create a new bank account named "Main Checking" of type "Bank" with an initial balance of 10,000 USD dated today, including additional details like the bank name and currency.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the bank account to be created. |
| Type | The type of the account. Options: Bank, Cash, Credit Card, Other. |
| Initial Balance | The starting balance of the account (number with two decimal precision). |
| Initial Balance Date | The date corresponding to the initial balance, formatted as YYYY-MM-DD. |
| Additional Fields | Optional extra information about the account, including: |
| - Description | A textual description of the account. |
| - Bank Name | The name of the bank associated with the account. |
| - Account Number | The bank account number. |
| - Currency | The currency code for the account. Options: COP (Colombian Peso), USD (US Dollar), EUR (Euro), MXN (Mexican Peso), ARS (Argentine Peso), PEN (Peruvian Sol), CLP (Chilean Peso). Default is COP. |
| - Status | Boolean indicating whether the account is active (true) or inactive (false). |
Output
The output JSON contains the response from the Alegra API after creating the bank account. This typically includes all details of the newly created bank account such as its unique identifier, name, type, initial balance, currency, status, and any other metadata returned by the API.
No binary data output is produced by this operation.
Example output snippet (simplified):
{
"id": "12345",
"name": "Main Checking",
"type": "bank",
"initialBalance": "10000.00",
"initialBalanceDate": "2024-06-01",
"currency": {
"code": "USD"
},
"status": true,
"description": "Primary checking account",
"bankName": "Bank of Example",
"number": "987654321"
}
Dependencies
- Requires an API key credential for authenticating with the Alegra API.
- The node uses the Alegra API base URL configured via the credential environment.
- Network connectivity to Alegra's API endpoints is necessary.
- No additional external libraries beyond n8n core dependencies are required.
Troubleshooting
- Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Validation errors: Missing required fields such as "Name", "Type", "Initial Balance", or "Initial Balance Date" will cause the API to reject the request. Verify all mandatory inputs are provided and correctly formatted.
- Date format issues: The "Initial Balance Date" must be in
YYYY-MM-DDformat. Incorrect formats may lead to errors. - Currency codes: Use one of the supported currency codes; unsupported codes may cause failures.
- API rate limits or downtime: If requests fail unexpectedly, check Alegra API status and ensure you are not exceeding rate limits.
Error messages from the node will typically contain the API error message. Review these messages to identify missing or invalid parameters.