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 automate financial budgeting tasks. Specifically, the "Get Transaction by Month" operation under the "Transactions" resource retrieves all transactions for a specified month within a YNAB budget.
This operation is useful for users who want to analyze or report on their spending and income activities for a particular month. For example, a user could use this node to fetch all transactions from March 2024 to generate monthly expense reports or to feed data into other automation workflows like accounting systems or dashboards.
Properties
| Name | Meaning |
|---|---|
| Month | The year and month for which to retrieve transactions. Only the year and month parts of the date are used. The input is a date-time type but only the "yyyy-MM" portion is relevant. |
Output
The output JSON contains the data returned by the YNAB API for transactions in the specified month. It includes an array of transaction objects with details such as:
- Transaction ID
- Date
- Amount (in milliunits, i.e., amount * 1000)
- Account ID
- Payee information
- Category ID
- Memo
- Cleared status
- Subtransactions (if any)
The structure matches the YNAB API's response for monthly transactions, encapsulated under a data property.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the YNAB API.
- Requires an API key credential configured in n8n for authenticating requests.
- The node dynamically determines the budget ID via a helper function before making API calls.
- Uses the Luxon library internally to format dates to the required "yyyy-MM" string format.
Troubleshooting
- Invalid or missing API credentials: Ensure that the API key credential is correctly set up in n8n; otherwise, authentication will fail.
- Incorrect month format: The node expects a valid ISO date-time input but uses only the year and month. Providing invalid dates may cause errors.
- Budget ID resolution failure: If the budget ID cannot be determined, the API call URL will be incorrect, leading to request failures.
- API rate limits or network issues: These can cause HTTP request failures; check connectivity and YNAB API status.
- Error messages: Errors thrown by the node include context about the item index for easier debugging. Use the error details to identify and fix input or configuration issues.
Links and References
This summary focuses solely on the static code analysis of the "Get Transaction by Month" operation within the "Transactions" resource of the YNAB node.