Actions22
- Accounts Actions
- Categories Actions
- Payees Actions
- Payee Locations Actions
- Months Actions
- Transactions Actions
- Scheduled Transactions Actions
Overview
This node integrates with the YNAB (You Need A Budget) API to retrieve financial transaction data filtered by category. Specifically, the "Get Transaction by Category" operation fetches all transactions associated with a specified category ID, optionally filtered by a starting date ("Since"). This is useful for users who want to analyze or report on spending within particular budget categories over time.
Practical examples include:
- Extracting all grocery-related transactions from a budget to analyze monthly food expenses.
- Fetching transactions in a "Utilities" category since the start of the year to track utility bills.
- Integrating with other systems to automate financial reporting based on category-specific spending.
Properties
| Name | Meaning |
|---|---|
| Category ID | The unique identifier of the category for which to fetch transactions. Required. |
| Since | Optional date filter to fetch transactions on or after this date (date only, time ignored). |
Output
The output JSON contains the raw response data from the YNAB API endpoint that lists transactions for the specified category. It includes details such as transaction IDs, dates, amounts, payees, memos, cleared status, and any subtransactions related to the category.
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 constructs the base URL using the budget ID obtained from credentials or helper functions.
- Uses the
luxonlibrary internally to format dates according to YNAB API requirements.
Troubleshooting
- Invalid Category ID: If the provided category ID does not exist or is incorrect, the API will return an error. Verify the category ID is correct and belongs to the connected budget.
- Date Format Issues: The "Since" property expects a valid ISO 8601 date string. Invalid or malformed dates may cause request failures.
- Authentication Errors: Ensure the API key credential is valid and has access to the specified budget.
- Empty Results: If no transactions are returned, verify that there are transactions in the category and that the "Since" date filter is not excluding all data.
Common error messages typically come from the YNAB API and relate to authentication, invalid parameters, or resource not found. Checking the input parameters and API credentials usually resolves these issues.