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 transactions within a specified budget. Specifically, the "Delete Transaction" operation allows users to remove a transaction from their YNAB budget by providing the transaction's unique identifier.
Common scenarios for this node include automating budget cleanup, removing erroneous or duplicate transactions, and integrating transaction management into broader financial workflows. For example, a user might set up an automation that deletes transactions flagged as duplicates in another system or removes test transactions after validation.
Properties
| Name | Meaning |
|---|---|
| Transaction ID | The unique identifier of the transaction to delete. This is required to specify which transaction should be removed from the budget. |
Output
The node outputs JSON data representing the deleted transaction as returned by the YNAB API. This typically includes details such as the transaction ID, date, amount, account, category, payee, memo, and cleared status prior to deletion.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the YNAB API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- Requires the budget ID to be set or retrieved dynamically, as it forms part of the API endpoint URL.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Transaction ID will result in an error from the YNAB API.
- Missing or incorrect API credentials will cause authentication failures.
- If the budget ID is not correctly set or accessible, the API request URL will be invalid.
Error Messages:
- "Transaction not found" — Verify the Transaction ID is correct and exists in the specified budget.
- Authentication errors — Check that the API key credential is valid and has necessary permissions.
- Invalid budget ID or URL errors — Ensure the budget ID is properly configured or retrieved.
Resolving these usually involves verifying input parameters, credentials, and budget configuration.