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 detailed information about a specific month within a user's budget. It is useful for automating financial workflows where you need to access monthly budget data, such as generating reports, syncing budget data with other tools, or analyzing spending patterns for a particular month.
For example, you can use this node to fetch all transactions, budgeted amounts, and activity for March 2024 in your YNAB budget, enabling automated monthly financial summaries or alerts.
Properties
| Name | Meaning |
|---|---|
| Specify Month | The year and month to retrieve data for. Only the year and month parts of the date are used; the day is ignored. |
Output
The node outputs JSON data representing the details of the specified month from the YNAB budget. This includes budget activity, available amounts, and transactions associated with that month as returned by the YNAB API's /months/{month} endpoint.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the YNAB API using an API key credential.
- The node expects a configured budget ID to construct the API request URL.
- Uses the
luxonlibrary internally to format the input date into the requiredyyyy-MMformat for the API call.
Troubleshooting
- Invalid Date Format: If the "Specify Month" property is not a valid ISO date string, the node may fail to format the date correctly. Ensure the input is a proper date/time string.
- Budget ID Missing or Incorrect: The node requires a valid budget ID credential. If missing or incorrect, API calls will fail with authentication or resource not found errors.
- API Rate Limits or Network Issues: Standard API errors related to rate limiting or connectivity may occur. Retrying after some time or checking network settings can help.
- Error Messages: Errors thrown by the node include context about which item caused the failure. Use this information to debug input data issues.