Overview
This node integrates with the ActualBudget API to manage budget data, specifically allowing users to import transactions into a specified budget account. It is useful for automating the process of adding multiple financial transactions to a budget, which can help in maintaining up-to-date budget records without manual entry.
A practical example would be importing a batch of bank transactions from an external source (like a CSV or another financial app) directly into a budget account, streamlining bookkeeping and financial tracking workflows.
Properties
| Name | Meaning |
|---|---|
| Budget ID | The unique identifier of the budget you want to work with. |
| Transactions | A JSON array representing the list of transactions to import into the budget account. |
Note: Although the bundled code shows an "Account ID" property used internally for the import operation, it was not provided in your input properties and thus is omitted here.
Output
The node outputs a JSON array where each element corresponds to the result of processing an input item. Each output item contains either the successful response from importing transactions or an error message if the operation failed for that item.
The json output field structure is an array of objects reflecting the import results per input item.
No binary data output is produced by this node.
Dependencies
- Requires access to the ActualBudget API.
- Needs an API authentication credential (an API key or password) configured in n8n to connect securely to the ActualBudget service.
- Uses the
@actual-app/apinpm package internally to interact with the ActualBudget API.
Troubleshooting
Common issues:
- Invalid or missing Budget ID will cause the node to fail when attempting to download or modify the budget.
- Incorrect or expired API credentials will prevent successful connection to the ActualBudget API.
- Malformed JSON in the Transactions property may cause errors during import.
Error messages:
- Errors related to authentication failures indicate problems with the API credentials; verify and update them as needed.
- Errors about budget download failure suggest the Budget ID might be incorrect or the budget does not exist.
- JSON parsing errors on the Transactions input require checking the format and correctness of the JSON data.
To handle errors gracefully, enable the "Continue On Fail" option in the node settings to allow processing of subsequent items even if one fails.