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 manage financial data related to budgets, accounts, categories, payees, months, transactions, and scheduled transactions. Specifically, for the Delete Transaction operation under the Transactions resource, it allows users to delete a specific transaction from their YNAB budget by providing the transaction ID.
Common scenarios where this node is beneficial include automating budget cleanup, removing erroneous or duplicate transactions, and integrating YNAB transaction management into broader workflow automations.
Example use case: Automatically deleting a transaction in YNAB when it is reversed or canceled in another financial system, ensuring budget data stays accurate without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Transaction ID | The unique identifier of the transaction to be deleted from the YNAB budget. |
Output
The output JSON contains the details of the deleted transaction as returned by the YNAB API. This typically includes all properties of the transaction before deletion, such as date, amount, account ID, payee, category, memo, and cleared status.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the YNAB API using an API key credential.
- The node expects a valid budget ID configured either via credentials or dynamically retrieved.
- Uses the n8n HTTP request helper with authentication to communicate with the YNAB REST API.
Troubleshooting
- Invalid Transaction ID: If the provided transaction ID does not exist or is incorrect, the API will return an error. Verify the transaction ID is correct and belongs to the specified budget.
- Authentication Errors: Ensure the API key credential is valid and has access to the target budget.
- Budget ID Issues: The node dynamically retrieves the budget ID; if this fails, check that the budget ID is correctly set in credentials or accessible via the API key.
- API Rate Limits: Frequent calls may hit YNAB API rate limits; handle errors gracefully and consider adding delays or retries.
- Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error details in the output.