YNAB icon

YNAB

Node for automating YNAB budget

Actions22

Overview

This node operation updates an existing scheduled transaction in a YNAB (You Need A Budget) budget. Scheduled transactions are recurring or planned transactions that occur on a set frequency, such as monthly bills or regular income.

Use cases include:

  • Modifying the amount, account, or frequency of a scheduled payment.
  • Changing payee or category details for better budgeting accuracy.
  • Adding or updating subtransactions to split the scheduled transaction into multiple parts.

For example, you might update a scheduled rent payment to increase the amount or change the payment frequency from monthly to every other month.

Properties

Name Meaning
Scheduled Transaction ID The unique identifier of the scheduled transaction to update.
Amount The total amount of the scheduled transaction. Must be a number with up to two decimal places.
Account ID The identifier of the account associated with this scheduled transaction.
Frequency How often the scheduled transaction occurs. Options: Never, Daily, Weekly, Every Other Week, Twice a Month, Every 4 Weeks, Monthly, Every Other Month, Every 3 Months, Every 4 Months, Twice a Year, Yearly, Every Other Year.
Additional Fields A collection of optional fields to further specify the scheduled transaction:
- Payee ID Identifier of the payee for the transaction.
- Payee Name Name of the payee. If Payee ID is not provided, this name will be used to find or create a payee.
- Category ID Identifier of the category for the transaction.
- Memo A note or memo attached to the transaction.
- Sub Transactions Multiple subtransactions that make up the total amount. Each subtransaction includes:
-- Amount Amount of the subtransaction (required).
-- Payee ID Payee identifier for the subtransaction.
-- Payee Name Payee name for the subtransaction; used if Payee ID is null.
-- Category ID Category identifier for the subtransaction. Credit Card Payment categories are ignored if supplied.
-- Memo Memo for the subtransaction.

Output

The output JSON contains the updated scheduled transaction object returned by the YNAB API. This includes all properties of the scheduled transaction after the update, such as:

  • id: Scheduled transaction identifier.
  • amount: Updated amount in milliunits (amount * 1000).
  • account_id: Associated account identifier.
  • frequency: Updated frequency string.
  • date: Date of the scheduled transaction.
  • payee_id and/or payee_name.
  • category_id.
  • memo.
  • subtransactions: Array of subtransaction objects with their respective details.

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 resolved.
  • Uses the Luxon library internally for date formatting.
  • Requires proper permissions on the YNAB API to update scheduled transactions.

Troubleshooting

  • Invalid Scheduled Transaction ID: If the provided ID does not exist, the API will return an error. Verify the ID is correct.
  • Amount Mismatch in Subtransactions: The sum of subtransaction amounts must equal the main amount; otherwise, subtransactions are ignored. Ensure amounts match exactly.
  • Invalid Frequency Value: Only predefined frequency options are accepted. Using an unsupported value will cause an error.
  • Date Format Issues: Dates must be ISO strings convertible to yyyy-MM-dd. Invalid dates will cause request failures.
  • API Authentication Errors: Ensure the API key credential is valid and has access to the specified budget.
  • Permission Denied: The API user must have rights to modify scheduled transactions in the budget.

To resolve errors, check input values carefully, confirm API credentials, and consult YNAB API documentation for detailed error messages.

Links and References

Discussion