YNAB icon

YNAB

Node for automating YNAB budget

Actions22

Overview

This node integrates with the YNAB (You Need A Budget) API to retrieve financial data related to payee locations. Specifically, the "Get Location by Payee" operation fetches all location details associated with a given payee ID within a specified budget. This is useful for scenarios where you want to analyze or manage the physical or registered locations tied to a payee, such as stores or service points linked to a vendor.

Practical examples include:

  • Retrieving all store locations of a particular vendor to display in a report.
  • Verifying the address information of a payee before processing transactions.
  • Automating workflows that depend on payee location data for budgeting or auditing purposes.

Properties

Name Meaning
Payee ID The unique identifier of the payee whose locations you want to retrieve.

Output

The node outputs JSON data containing the list of payee locations associated with the specified payee ID. The structure corresponds to the YNAB API response for payee locations and typically includes fields such as location IDs, addresses, city, state, postal code, latitude, longitude, and other relevant location metadata.

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 expects a valid budget ID to be set either via credentials or dynamically retrieved.
  • Uses HTTP requests authenticated against the YNAB API endpoint https://api.ynab.com/v1/budgets/{budgetId}.

Troubleshooting

  • Common issues:

    • Invalid or missing Payee ID: Ensure the Payee ID provided exists in your YNAB budget.
    • Authentication errors: Verify that the API key credential is correctly configured and has access to the specified budget.
    • Budget ID not found or incorrect: Confirm the budget ID is correct and accessible by the API key.
    • Network or API downtime: Check internet connectivity and YNAB API status.

  • Error messages:

    • Authorization errors (e.g., 401 Unauthorized): Usually caused by invalid API keys; reconfigure credentials.
    • Not Found errors (e.g., 404): Occur if the payee or budget does not exist; verify IDs.
    • Rate limiting or quota exceeded: Wait and retry later or check API usage limits.

Links and References

Discussion