YNAB icon

YNAB

Node for automating YNAB budget

Actions22

Overview

This node integrates with the YNAB (You Need A Budget) API to automate budget management tasks. Specifically, the "Get Transaction by Payee" operation fetches all transactions associated with a specified payee, optionally filtered by a starting date. This is useful for users who want to analyze or report on spending related to a particular payee, such as a vendor or service provider.

Practical examples include:

  • Retrieving all transactions paid to a specific utility company since the beginning of the year.
  • Monitoring expenses related to a frequent payee to track spending habits.
  • Generating reports or alerts based on transactions from a particular payee.

Properties

Name Meaning
Payee ID The unique identifier of the payee whose transactions you want to retrieve.
Since Optional date filter to fetch transactions on or after this date (date only, time ignored).

Output

The output JSON contains the data returned by the YNAB API for transactions related to the specified payee. It includes an array of transaction objects with details such as amount, date, category, memo, and cleared status.

Example structure snippet:

{
  "data": {
    "transactions": [
      {
        "id": "string",
        "date": "YYYY-MM-DD",
        "amount": number,
        "memo": "string",
        "cleared": "cleared_status",
        "category_id": "string",
        "payee_id": "string",
        ...
      }
      // more transactions
    ]
  }
}

No binary data output is involved in this operation.

Dependencies

  • Requires an active YNAB API key credential configured in n8n.
  • Needs the budget ID to be set either via credentials or dynamically resolved.
  • Uses the YNAB REST API endpoint https://api.ynab.com/v1/budgets/{budgetId}/payees/{payeeId}/transactions.

Troubleshooting

  • Common issues:

    • Invalid or missing Payee ID will cause the API request to fail.
    • Incorrect or expired API key credential will result in authentication errors.
    • If the "Since" date is malformed or invalid, the date filter may not apply correctly.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • Authentication errors typically indicate problems with the API key; verify and update credentials.
    • "Not Found" errors may mean the payee ID does not exist in the specified budget.
    • Rate limiting errors from YNAB API require waiting before retrying requests.

Links and References

Discussion