YNAB icon

YNAB

Node for automating YNAB budget

Actions22

Overview

This node integrates with the YNAB (You Need A Budget) API to manage scheduled transactions within a user's budget. Specifically, the "Delete Scheduled Transaction" operation allows users to remove a scheduled transaction by its ID. This is useful for automating budget adjustments, such as canceling recurring payments or planned expenses that are no longer relevant.

Practical examples include:

  • Automatically deleting a scheduled subscription payment when a user cancels the service.
  • Removing planned future transactions that were entered in error.
  • Managing and cleaning up scheduled transactions as part of a larger financial automation workflow.

Properties

Name Meaning
Scheduled Transaction ID The unique identifier of the scheduled transaction to delete. This is required to specify which scheduled transaction should be removed.

Output

The output JSON contains the deleted scheduled transaction's data as returned by the YNAB API. This typically includes details such as the transaction ID, amount, date, account, payee, category, memo, frequency, and any subtransactions that were part of it.

No binary data is output by this operation.

Example output structure (simplified):

{
  "scheduled_transaction": {
    "id": "string",
    "amount": 12345,
    "date": "YYYY-MM-DD",
    "account_id": "string",
    "payee_id": "string",
    "category_id": "string",
    "memo": "string",
    "frequency": "string",
    "subtransactions": []
  }
}

Dependencies

  • Requires an active connection to the YNAB API using an API key credential.
  • The node expects the budget ID to be configured or retrievable via credentials or parameters.
  • Uses HTTP requests authenticated with the provided API key to communicate with YNAB's REST API.

Troubleshooting

  • Common issues:

    • Invalid or missing Scheduled Transaction ID will cause the API call to fail.
    • Incorrect or expired API key credential will result in authentication errors.
    • Attempting to delete a scheduled transaction that does not exist or belongs to a different budget will return an error.
    • Network connectivity problems can prevent successful API calls.

  • Error messages and resolutions:

    • 401 Unauthorized: Check that the API key credential is valid and has proper permissions.
    • 404 Not Found: Verify the Scheduled Transaction ID is correct and exists in the specified budget.
    • 400 Bad Request: Ensure all required parameters are correctly set and formatted.
    • Network Errors: Confirm internet connectivity and that the YNAB API endpoint is reachable.

Links and References

Discussion