YNAB - Get Categories

YNAB Get Categories

Overview

This node retrieves category data from a specified budget in the YNAB (You Need A Budget) system. It is useful for users who want to programmatically access their budgeting categories, for example, to analyze spending patterns, generate reports, or integrate budget categories into other workflows.

Practical examples include:

  • Automatically fetching all categories of a budget to display them in a dashboard.
  • Syncing YNAB categories with another financial tool or database.
  • Triggering actions based on category data changes.

Properties

Name Meaning
Budget ID The identifier of the budget from which to retrieve categories. Users should provide the correct budget ID as found in their YNAB account.

Output

The node outputs an array of items where each item contains a json object with a single field:

  • response: This field holds the full JSON response returned by the YNAB API for the categories endpoint. It includes detailed information about all categories within the specified budget.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the YNAB API using an API key credential configured in n8n.
  • The node uses the YNAB REST API endpoint: https://api.ynab.com/v1/budgets/{budget_id}/categories.
  • Proper configuration of the API authentication credential in n8n is necessary for successful requests.

Troubleshooting

  • Common issues:

    • Invalid or missing Budget ID: Ensure the Budget ID provided matches one from your YNAB account.
    • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
    • Network or API downtime: Check internet connectivity and YNAB API status.
  • Error messages:

    • If the node throws an error related to HTTP request failure, it usually indicates authentication problems or invalid parameters. Double-check the Budget ID and API credentials.
    • Errors from the YNAB API will be wrapped and presented as node errors; reviewing the error message can help identify issues like rate limits or permission denials.

Links and References

Discussion