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 budget management tasks. Specifically, for the Scheduled Transactions resource and the Get Scheduled Transaction operation, it retrieves detailed information about a single scheduled transaction by its unique ID within a specified budget.
Common scenarios where this node is beneficial include:
- Fetching details of a recurring payment or income scheduled in YNAB.
- Automating financial workflows that depend on upcoming scheduled transactions.
- Integrating scheduled transaction data into reporting or notification systems.
For example, you could use this node to get the next scheduled rent payment or subscription charge details automatically and trigger alerts or further processing based on that data.
Properties
| Name | Meaning |
|---|---|
| Scheduled Transaction ID | The unique identifier of the scheduled transaction to retrieve. This is required input. |
Output
The node outputs a JSON object representing the scheduled transaction details as returned by the YNAB API. This includes all properties of the scheduled transaction such as amount, date, account ID, frequency, payee information, category, memo, and any subtransactions if present.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the YNAB API using an API key credential configured in n8n.
- Needs the budget ID to be set either via credentials or dynamically resolved at runtime.
- Uses HTTP requests authenticated with the provided API key to communicate with the YNAB REST API.
Troubleshooting
- Invalid Scheduled Transaction ID: If the provided ID does not exist or is malformed, the API will return an error. Verify the ID is correct and belongs to the specified budget.
- Authentication Errors: Ensure the API key credential is valid and has access to the target budget.
- Budget ID Resolution: If the budget ID is missing or incorrect, the request URL will be invalid. Confirm the budget ID is properly configured or passed.
- Network Issues: Connectivity problems can cause request failures; check network access to the YNAB API endpoint.
If errors occur, the node will throw descriptive messages including HTTP status codes and error details from the YNAB API response.
Links and References
- YNAB API Documentation - Scheduled Transactions
- YNAB Official Website
- n8n Documentation - HTTP Request Node (for understanding underlying HTTP calls)