YNAB

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.

Typical use cases include:

• Fetching details of a recurring payment or income scheduled in your budget.
• Automating reports or workflows that require up-to-date information on scheduled transactions.
• Integrating scheduled transaction data into other systems for financial planning or analysis.

For example, you might use this node to get the next scheduled rent payment or subscription charge details automatically as part of a monthly budgeting workflow.

Properties

Output

The node outputs a JSON object representing the requested scheduled transaction. The structure corresponds to the YNAB API's scheduled transaction object, which typically includes fields such as:

• id: Unique identifier of the scheduled transaction.
• date: The date when the transaction is scheduled.
• amount: The amount of money involved (in milliunits, i.e., multiplied by 1000).
• account_id: Identifier of the account associated with the transaction.
• payee_id / payee_name: Information about the payee.
• category_id: Category assigned to the transaction.
• memo: Optional note or description.
• frequency: How often the transaction recurs (e.g., monthly, weekly).
• subtransactions: Any subtransactions included.

No binary data output is produced by this operation.

Dependencies

• Requires an active connection to the YNAB API via an API key credential.
• The node expects a valid budget ID to be configured or dynamically retrieved.
• Uses HTTP requests authenticated with the provided API key to communicate with YNAB's REST API.

Troubleshooting

• Common issues:

  • Invalid or missing Scheduled Transaction ID will cause the API call to fail.
  • Incorrect or expired API credentials will result in authentication errors.
  • If the budget ID is not set correctly, the node cannot construct the proper API endpoint URL.
  • Network connectivity problems can prevent successful API calls.

• Error messages:

  • Authentication errors usually indicate invalid API keys; verify and update credentials.
  • "Not Found" errors suggest the Scheduled Transaction ID does not exist in the specified budget.
  • Validation errors may occur if the Scheduled Transaction ID format is incorrect.

• Resolutions:

  • Double-check the Scheduled Transaction ID input for correctness.
  • Ensure the API key credential is valid and has appropriate permissions.
  • Confirm the budget ID is properly configured in the node or credentials.
  • Test network connectivity and retry if transient issues occur.

Links and References

• YNAB API Documentation - Scheduled Transactions
• YNAB Official Website
• n8n Documentation - Creating Custom Nodes