Actions15
Overview
This node integrates with the YNAB (You Need A Budget) API to update an existing transaction within a specified budget. It allows users to modify details such as the account associated with the transaction, the date, amount, payee name, memo, and cleared status. This is useful for keeping budget records accurate and up-to-date when transactions change or need correction.
Practical examples include:
- Correcting the amount of a previously recorded transaction.
- Changing the payee name or memo for clarity.
- Updating the cleared status after reconciling bank statements.
- Moving a transaction to a different account within the same budget.
Properties
| Name | Meaning |
|---|---|
| Budget ID | The unique identifier of the budget containing the transaction to update. |
| Transaction ID | The unique identifier of the transaction to be updated. |
| Account ID | The identifier of the account associated with the transaction. |
| Date | The date of the transaction in ISO format (YYYY-MM-DD). |
| Amount | The transaction amount expressed in milliunits (e.g., 1000 = 1.00 unit of currency). |
| Payee Name | The name of the payee involved in the transaction. |
| Memo | Additional notes or description related to the transaction. |
| Cleared | The cleared status of the transaction; possible values are: Cleared, Uncleared, Reconciled. |
Output
The node outputs a JSON object representing the updated transaction. The structure corresponds to the YNAB API's transaction object, typically including fields like transaction ID, account ID, date, amount, payee name, memo, cleared status, and other metadata returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the YNAB API via an API key credential.
- The node must be configured with valid authentication credentials that allow access to the user's budgets and transactions.
- Network connectivity to
https://api.ynab.com/v1is necessary.
Troubleshooting
Common issues:
- Invalid or missing Budget ID or Transaction ID will cause the API request to fail.
- Incorrect formatting of the date (not ISO YYYY-MM-DD) may result in validation errors.
- Insufficient permissions or invalid API key can lead to authorization errors.
- Providing an Account ID that does not belong to the specified budget may cause errors.
Error messages and resolutions:
- "404 Not Found" — Check that the Budget ID and Transaction ID exist and are correct.
- "401 Unauthorized" — Verify that the API key credential is valid and has proper scopes.
- "400 Bad Request" — Ensure all required fields are provided and correctly formatted, especially date and amount.
- "422 Unprocessable Entity" — Confirm that the Account ID belongs to the budget and that the cleared status value is one of the allowed options.