Overview
This node integrates with the ActualBudget API to import financial transactions into a specified budget and account. It is designed to automate the process of adding multiple transactions in bulk, which can be useful for syncing external financial data sources or batch uploading transaction records.
Common scenarios include:
- Importing bank or credit card transactions into an ActualBudget account.
- Automating transaction uploads from other financial software.
- Bulk updating budgets with new spending or income entries.
For example, a user could export transactions from their bank as JSON and use this node to import them directly into their ActualBudget account, saving manual entry time.
Properties
| Name | Meaning |
|---|---|
| Budget ID | The unique identifier of the budget you want to work with. |
| Account ID | The unique identifier of the account within the budget where transactions will be added. |
| Transactions | A JSON array representing the list of transactions to import into the specified account. |
Output
The node outputs a JSON array where each element corresponds to the result of importing transactions for each input item. Each output item contains the response or status related to the import operation.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the ActualBudget API.
- Uses the
@actual-app/apipackage to interact with the ActualBudget service. - The node downloads the specified budget before importing transactions and shuts down the API client after execution.
Troubleshooting
- Authentication errors: Ensure that the API key credential is correctly configured and has the necessary permissions.
- Invalid Budget ID or Account ID: Verify that the provided IDs exist and are correct; otherwise, the import will fail.
- Malformed Transactions JSON: The transactions property must be a valid JSON array; invalid JSON will cause errors.
- API connectivity issues: Network problems or incorrect server URLs in credentials may prevent successful communication with the ActualBudget API.
If the node throws errors during import, enabling "Continue On Fail" allows processing subsequent items without stopping the entire workflow.
Links and References
- ActualBudget API Documentation (general reference)
- n8n Documentation on Creating Custom Nodes