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 Transaction by Payee" operation fetches all transactions associated with a specified payee within a budget. This is useful for users who want to analyze spending patterns related to a particular payee or vendor.

Common scenarios include:

Retrieving all transactions from a specific payee to review expenses.
Filtering transactions starting from a certain date to track recent payments.
Automating financial reports based on payee-specific data.

Example: A user wants to get all transactions paid to "Electric Company" since January 1, 2024, to verify monthly utility expenses.

Properties

Name	Meaning
Payee ID	The unique identifier of the payee whose transactions you want to retrieve.
Since	Optional date filter to fetch transactions on or after this date (date only, time ignored).

Output

The output JSON contains the data returned by the YNAB API for transactions linked to the specified payee. It includes an array of transaction objects with details such as amount, date, account, category, memo, and cleared status.

No binary data is output by this operation.

Dependencies

Requires an active connection to the YNAB API using an API key credential.
The node expects a configured budget ID either via credentials or node parameters.
Uses the luxon library internally for date formatting.
Requires n8n HTTP Request helper with authentication support for making API calls.

Troubleshooting

Invalid Payee ID: If the provided payee ID does not exist in the budget, the API will return an error or empty results. Verify the payee ID is correct.
Authentication Errors: Ensure the API key credential is valid and has access to the specified budget.
Date Format Issues: The "Since" property must be a valid ISO date string; otherwise, the node may fail or ignore the filter.
API Rate Limits: Frequent requests might hit YNAB API rate limits; consider adding delays or handling retries.