YNAB

Node for automating YNAB budget

Actions22

Accounts Actions
- Get Account
- Create Account
Categories Actions
- Get Category
- Update Category
Payees Actions
- Get Payee
- Update Payee
Payee Locations Actions
- Get Location by ID
- Get Location by Payee
Months Actions
- Get Month
Transactions Actions
Scheduled Transactions Actions

Overview

This node integrates with the YNAB (You Need A Budget) API to automate budget management tasks. Specifically, the "Get Account" operation under the "Accounts" resource retrieves detailed information about a single account within a specified YNAB budget.

Typical use cases include:

Fetching details of a specific bank or cash account to display or process in workflows.
Integrating YNAB account data into reporting or financial dashboards.
Automating synchronization of account information between YNAB and other financial tools.

For example, you might use this node to get the current balance and metadata of a checking account by providing its unique Account ID.

Properties

Name	Meaning
Account ID	The unique identifier of the account to retrieve from the YNAB budget. This is required.

Output

The node outputs a JSON object representing the requested account's details as returned by the YNAB API. The structure typically includes fields such as:

id: The account's unique identifier.
name: The name of the account.
type: The type of account (e.g., checking, savings).
balance: The current balance in the account, represented in milliunits (thousandths of the currency unit).
cleared_balance and uncleared_balance: Balances reflecting cleared and uncleared transactions.
Other metadata like on_budget status, closed flag, and last modification date.

No binary data output is produced by this operation.

Dependencies

Requires an active connection to the YNAB API via an API key credential configured in n8n.
The node dynamically constructs the base URL using the budget ID obtained from credentials or parameters.
Uses HTTP requests authenticated with the provided API key to communicate with YNAB endpoints.

Troubleshooting

Invalid Account ID: If the provided Account ID does not exist or is mistyped, the API will return an error indicating the account was not found. Verify the Account ID is correct.
Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Ensure the API key is correctly set up in n8n credentials.
Budget ID Issues: The node requires a valid budget ID to form the API URL. If the budget ID is missing or incorrect, requests will fail. Confirm the budget ID is properly configured.
Network or API Downtime: Temporary network issues or YNAB API outages can cause request failures. Retry after some time or check YNAB service status.

Error messages thrown by the node will generally reflect these issues and include HTTP status codes and descriptive messages from the YNAB API.