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.
  • Integrating YNAB transaction data into broader accounting or budgeting automation pipelines.

Example use case:

  • You want to automatically retrieve a transaction's details after it has been created or updated in YNAB to log it in an external system or trigger further processing.

Properties

Name Meaning
Transaction ID The unique identifier of the transaction to retrieve. This is required to specify which transaction to get.

Output

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

  • id: Unique transaction 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 included.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the YNAB API via an API key credential configured in n8n.
  • The node dynamically constructs the base URL using the budget ID obtained from credentials or configuration.
  • Uses the luxon library internally for date formatting but this is abstracted away from the user.

Troubleshooting

  • Common issues:

    • Invalid or missing Transaction ID will cause the API call to fail.
    • Incorrect or missing budget ID in credentials can lead to authorization errors.
    • Network connectivity issues may prevent successful API requests.

  • Error messages:

    • Errors returned from the YNAB API typically include HTTP status codes and messages indicating the problem (e.g., 404 if the transaction does not exist).
    • If the node throws an error mentioning authentication failure, verify that the API key credential is correctly set up.
    • For date-related errors, ensure the transaction ID is valid and corresponds to the correct budget.

  • Resolution tips:

    • Double-check the Transaction ID input for correctness.
    • Confirm that the budget ID and API key are properly configured in n8n credentials.
    • Use the "Continue on Fail" option in the node settings to handle errors gracefully in workflows.

Links and References

Discussion