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 Account resource with the Get All operation, it retrieves all accounts associated with a specified budget.
Common scenarios where this node is beneficial include:
- Fetching a list of all accounts within a particular budget to display or process in workflows.
- Synchronizing account data from YNAB into other systems or databases.
- Automating financial reporting by pulling account details regularly.
Practical example:
- A user wants to generate a report of all their checking, savings, and credit card accounts under a specific budget. Using this node, they provide the budget ID and retrieve all accounts in one call, which can then be used downstream in the workflow.
Properties
| Name | Meaning |
|---|---|
| Budget ID | The ID of the budget for which to retrieve all accounts. This is a required string input. |
Output
The output JSON contains an array of account objects under the json field. Each account object includes detailed information about an individual account within the specified budget, such as its name, type, balance, and other metadata as provided by the YNAB API.
No binary data output is produced 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}/accounts - Proper configuration of the API key credential in n8n is necessary for successful authentication.
Troubleshooting
Common issues:
- Invalid or missing Budget ID: The API will not return accounts if the budget ID is incorrect or empty.
- Authentication errors: If the API key credential is invalid or expired, the request will fail.
- Network connectivity problems may prevent reaching the YNAB API endpoint.
Error messages and resolutions:
- 401 Unauthorized: Check that the API key credential is correctly set up and has proper permissions.
- 404 Not Found: Verify that the Budget ID exists and is accessible by the authenticated user.
- 400 Bad Request: Ensure the Budget ID parameter is provided and correctly formatted.