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 "Months" resource with the "Get Month" operation allows users to retrieve detailed information about a specific month within their budget. This can include budgeted amounts, activity, and available funds for that month.

Common scenarios where this node is beneficial include:

Fetching monthly budget summaries to analyze spending patterns.
Automating reports or dashboards that track budget performance by month.
Integrating monthly budget data into other financial tools or workflows.

For example, a user might specify a particular month (e.g., March 2024) to get all budget details for that month, enabling them to review how much was budgeted, spent, and what remains available.

Properties

Name	Meaning
Specify Month	The target month to retrieve data for. Only the year and month parts of the date are used.

The "Specify Month" property expects a date-time input, but only the year and month components are utilized to form the API request.

Output

The output JSON contains detailed information about the specified month in the YNAB budget. This includes fields such as:

Budgeted amounts for each category.
Activity (spending) during the month.
Available funds remaining.
Other metadata related to the month's budget status.

The structure corresponds directly to the YNAB API's month object returned from the endpoint /budgets/{budgetId}/months/{month}.

No binary data is output by this operation.

Dependencies

Requires an active connection to the YNAB API using an API key credential configured in n8n.
The node dynamically retrieves the budget ID from credentials or configuration.
Uses the luxon library internally to format dates correctly for the API request.
Requires internet access to communicate with the YNAB API endpoint.

Troubleshooting

Invalid Date Format: If the "Specify Month" property is not a valid ISO date string, the node may fail to format the date properly. Ensure the input is a valid date-time string.
Unauthorized Access: Errors related to authentication usually indicate missing or invalid API keys. Verify that the API key credential is correctly set up.
Budget ID Missing or Incorrect: The node depends on a valid budget ID. If the budget ID is not configured or incorrect, API calls will fail.
API Rate Limits: Frequent requests may hit YNAB API rate limits, causing errors. Implement retries or reduce request frequency if needed.
Network Issues: Connectivity problems will prevent successful API calls.

Error messages thrown by the node typically originate from the YNAB API responses or HTTP request failures. Review error details for guidance on resolving issues.