Actions22
- Accounts Actions
- Categories Actions
- Payees Actions
- Payee Locations Actions
- Months Actions
- Transactions Actions
- Scheduled Transactions Actions
Overview
This node integrates with the YNAB (You Need A Budget) API to automate budget management tasks. Specifically, the "Update Payee" operation under the "Payees" resource allows users to update details of an existing payee in their YNAB budget. This is useful for keeping payee information current, such as correcting names or updating payee details after changes.
Practical examples include:
- Renaming a payee to reflect a new business name.
- Correcting typos in payee names.
- Standardizing payee names for better reporting and categorization.
Properties
| Name | Meaning |
|---|---|
| Payee ID | The unique identifier of the payee to update. |
| Name | The new name to assign to the payee. |
Output
The node outputs JSON data representing the updated payee object returned by the YNAB API. This includes all relevant payee details after the update has been applied.
Example structure of the output JSON (json field):
{
"id": "string",
"name": "string",
"transfer_account_id": "string or null",
"deleted": false,
"payee_location_id": "string or null"
}
(Note: Actual fields depend on YNAB API response but generally include payee id, name, and related 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 dynamically constructs the base URL using the budget ID from credentials or configuration.
- Uses HTTP requests authenticated via the provided API key to interact with YNAB endpoints.
Troubleshooting
Common issues:
- Invalid or missing Payee ID will cause the API request to fail.
- Providing an empty or invalid name may result in validation errors from the API.
- Network or authentication failures if the API key is incorrect or expired.
- Budget ID misconfiguration can lead to 404 errors when accessing the API.
Error messages:
- Errors from the YNAB API are passed through; typical messages include "Payee not found" or "Invalid request body".
- Authentication errors indicate problems with the API key setup.
Resolutions:
- Verify that the Payee ID exists and is correct.
- Ensure the "Name" property is non-empty and valid.
- Confirm API key credentials are correctly set up in n8n.
- Check that the budget ID used in the node matches an existing budget in YNAB.
Links and References
- YNAB API Documentation - Payees
- YNAB Official Website
- n8n Documentation - HTTP Request Node (for understanding HTTP calls)