YNAB icon

YNAB

Node for automating YNAB budget

Overview

This node integrates with the YNAB (You Need A Budget) API to automate financial budgeting tasks. Specifically, the "List Transactions" operation under the "Transactions" resource fetches a list of transactions from a specified YNAB budget. It supports filtering transactions by a starting date, allowing users to retrieve only recent or relevant transaction data.

Common scenarios where this node is beneficial include:

  • Synchronizing recent financial transactions into other systems for reporting or analysis.
  • Automating bookkeeping workflows by fetching updated transaction lists regularly.
  • Filtering transactions since a particular date to track spending patterns or reconcile accounts.

For example, a user can configure this node to fetch all transactions from their YNAB budget starting from January 1st, 2024, and then use that data to generate monthly expense reports automatically.

Properties

Name Meaning
Since Fetch transactions on or after this date (date only, time ignored). If empty, fetches all.

Output

The node outputs JSON data containing the transactions retrieved from the YNAB API. The structure corresponds to the API's response format for transactions and includes details such as transaction IDs, dates, amounts, payees, categories, memos, and cleared status.

If the "Since" property is set, only transactions on or after that date are included in the output.

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.
  • The node dynamically constructs the base URL using the budget ID obtained from credentials or helper functions.
  • Uses the luxon library internally for date formatting.
  • Requires proper network access to the YNAB API endpoint.

Troubleshooting

  • Common issues:
    • Invalid or missing API authentication token will cause authorization errors.
    • Incorrect budget ID configuration may result in 404 Not Found errors.
    • Providing an invalid date format for the "Since" property could lead to request failures.
  • Error messages:
    • Authorization errors typically indicate problems with the API key; verify and update credentials.
    • HTTP 404 errors suggest the budget ID does not exist or is inaccessible; confirm the budget ID.
    • Date parsing errors may occur if the "Since" date is malformed; ensure it is a valid ISO date string.

Links and References

Discussion