Actions15
Overview
This node integrates with the YNAB (You Need A Budget) API to manage financial data related to budgets, accounts, transactions, categories, payees, and user information. Specifically, for the Transaction - Get All operation, it retrieves all transactions associated with a specified budget.
Common scenarios where this node is beneficial include:
- Fetching all transaction records for a particular budget to analyze spending patterns.
- Integrating YNAB transaction data into other workflows or reporting tools.
- Automating financial reconciliation by pulling transaction lists regularly.
For example, a user might use this node to get all transactions from their monthly budget to generate a custom report or trigger alerts based on spending thresholds.
Properties
| Name | Meaning |
|---|---|
| Budget ID | The ID of the budget whose transactions you want to retrieve. This is a required string input. |
Output
The output contains a JSON array under the json field representing the list of transactions retrieved from the specified budget. Each transaction object includes details such as transaction ID, account ID, date, amount (in milliunits), payee name, memo, and cleared status.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the YNAB API.
- The node makes HTTP GET requests to the endpoint:
https://api.ynab.com/v1/budgets/{budgetId}/transactions - Proper configuration of the API key credential in n8n is necessary for successful authentication.
Troubleshooting
- Missing or invalid Budget ID: The operation requires a valid budget ID. Ensure that the Budget ID property is correctly set and corresponds to an existing budget in YNAB.
- Authentication errors: If the API key credential is missing, invalid, or expired, the node will fail to authenticate. Verify the API key and update it if necessary.
- API rate limits: Frequent calls may hit YNAB API rate limits, resulting in errors. Implement retry logic or reduce call frequency.
- Network issues: Connectivity problems can cause request failures. Check network access and proxy settings if applicable.