YNAB icon

YNAB

Node for automating YNAB budget

Actions22

Overview

This node integrates with the YNAB (You Need A Budget) API to manage financial data related to budgets, accounts, categories, payees, months, transactions, and scheduled transactions. Specifically, for the Transactions resource and the Get Transaction operation, it retrieves detailed information about a single transaction by its unique ID within a specified budget.

Common scenarios where this node is beneficial include:

  • Fetching details of a specific transaction for review or reporting.
  • Automating workflows that require transaction data retrieval, such as syncing with other financial tools or generating custom notifications.
  • Auditing or reconciling transactions programmatically.

Example: You want to get the details of a particular transaction in your YNAB budget to verify its amount, date, category, and payee before processing it further in your workflow.

Properties

Name Meaning
Transaction ID The unique identifier of the transaction to retrieve. This is a required string input.

Output

The node outputs a JSON object representing the transaction details retrieved from YNAB. The structure corresponds to the YNAB API's transaction object, typically including fields such as:

  • id: Transaction unique identifier.
  • date: Date of the transaction.
  • amount: Amount of the transaction in milliunits (thousandths of the currency unit).
  • account_id: Identifier of the account associated with the transaction.
  • payee_id / payee_name: Payee information.
  • category_id: Category assigned to the transaction.
  • memo: Optional memo or note.
  • cleared: Cleared status of the transaction.
  • subtransactions: Any subtransactions if applicable.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the YNAB API via an API key credential.
  • The node expects a configured budget ID either through credentials or parameters to construct the API endpoint URL.
  • Uses the n8n helper method for authenticated HTTP requests to communicate with the YNAB API.

Troubleshooting

  • Common issues:

    • Invalid or missing Transaction ID will cause the API call to fail.
    • Incorrect or missing budget ID configuration will result in failed requests.
    • Network or authentication errors if the API key is invalid or expired.

  • Error messages:

    • Errors returned from the YNAB API will be propagated, often indicating "Not Found" if the transaction ID does not exist.
    • Authentication errors if the API key is invalid or missing.

  • Resolutions:

    • Ensure the Transaction ID is correct and exists in the specified budget.
    • Verify that the API key credential is properly set up and has access to the budget.
    • Confirm the budget ID is correctly provided or configured.
    • Check network connectivity and API service status.

Links and References

Discussion