YNAB icon

YNAB

Node for automating YNAB budget

Actions22

Overview

This node integrates with the YNAB (You Need A Budget) API to automate budget management tasks. Specifically, for the Scheduled Transactions resource and the Delete Scheduled Transaction operation, it allows users to delete a scheduled transaction from their YNAB budget.

This is useful in scenarios where you want to programmatically remove recurring or planned transactions that are no longer relevant, such as canceled subscriptions, changed payment plans, or corrected budgeting errors.

Practical example:

  • Automatically deleting a scheduled transaction when a subscription is canceled in another system.
  • Cleaning up outdated scheduled payments after a financial review.

Properties

Name Meaning
Scheduled Transaction ID The unique identifier of the scheduled transaction you want to delete. This is required.

Output

The output JSON contains the deleted scheduled transaction data returned by the YNAB API. It typically includes details about the scheduled transaction that was removed, such as its ID, amount, date, frequency, account, payee, category, and memo.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the YNAB API via an API key credential configured in n8n.
  • The node uses the budget ID from credentials or environment to construct API requests.
  • The node depends on the helpers.httpRequestWithAuthentication method to perform authenticated HTTP calls to the YNAB API.

Troubleshooting

  • Common issues:

    • Invalid or missing Scheduled Transaction ID will cause the API call to fail.
    • Incorrect or expired API authentication token will result in authorization errors.
    • Using a wrong budget ID or insufficient permissions can lead to "not found" or "access denied" errors.

  • Error messages and resolutions:

    • "404 Not Found" — Verify the Scheduled Transaction ID exists in the specified budget.
    • "401 Unauthorized" — Check that the API key credential is valid and has proper access.
    • "400 Bad Request" — Ensure the Scheduled Transaction ID is correctly formatted and provided.
    • If the node throws a NodeOperationError with context, inspect the item index to identify which input caused the failure.

Links and References

Discussion