# YNAB AI integration on Definable

> YNAB (You Need A Budget) is a budgeting tool helping users track expenses, plan finances, and gain control over spending to reduce debt

## What this connects

YNAB (You Need A Budget) is a budgeting tool helping users track expenses, plan finances, and gain control over spending to reduce debt

Vendor: https://www.ynab.com

## Tools available

**27** tools available. First 12:

- `YNAB_CREATE_ACCOUNT` — Create a new account in a budget — Tool to create a new account in a budget. Use when you need to add a manual (non-linked) account to a specific budget.
- `YNAB_CREATE_SCHEDULED_TRANSACTION` — Create Scheduled Transaction — Creates a scheduled (recurring) transaction in a YNAB budget. Use this to set up bills, recurring expenses, or income that repeats on a schedule. Requires an account_id (from YNAB_LIST_ACCOUNTS), a date, frequency, and amount in milliunits.
- `YNAB_DELETE_SCHEDULED_TRANSACTION` — Delete Scheduled Transaction — Permanently deletes a scheduled transaction from a YNAB budget. Use this when a recurring transaction is no longer needed. This action cannot be undone. Obtain the scheduled_transaction_id from list_scheduled_transactions or get_scheduled_transaction_by_id before calling this.
- `YNAB_GET_ACCOUNT_BY_ID` — Get Account by ID — Tool to retrieve a single account resource. Use when you need details of a specific account by its ID after determining the budget.
- `YNAB_GET_BUDGET_BY_ID` — Get Budget By ID — Retrieve a complete budget export by ID, including all accounts, categories, payees, and transactions. Use this tool when you need comprehensive budget data. The response includes: - Budget metadata (name, date/currency formats) - All accounts with balances - Category groups and categories with budgeted amounts and balances - All payees - All transactions and scheduled transactions (optional, may be large) For incremental syncing, use last_knowledge_of_server to only fetch changes since your last request. Note: Currency amounts are in 'milliunits' format (divide by 1000 for standard units).
- `YNAB_GET_BUDGET_MONTH` — Get Budget Month — Tool to retrieve a specific budget month. Use when you need detailed summary and category budgets for a given month after confirming the budget ID. Monetary amounts are returned in milliunits (divide by 1000 for standard currency). Response includes high-level aggregates and a nested category array within the month payload for per-category budget analysis.
- `YNAB_GET_BUDGET_SETTINGS` — Get Budget Settings — Tool to retrieve budget-level settings. Use when you need to fetch currency and date formatting preferences for a specific budget.
- `YNAB_GET_CATEGORY_BY_ID` — Get Category by ID — Retrieve a single YNAB budget category by its ID. Use this to get detailed category information including budgeted amounts, activity, balance, and goal settings. Amounts are returned for the current budget month (UTC). Requires both budget_id and category_id - use 'last-used' or 'default' for budget_id if you don't have a specific budget ID.
- `YNAB_GET_MONTH_CATEGORY_BY_ID` — Get Month Category By ID — Tool to retrieve a single category for a specific budget month. Use after selecting the budget and month when you need month-specific category details.
- `YNAB_GET_PAYEE_BY_ID` — Get Payee by ID — Tool to retrieve a single payee by its ID. Use when you need full details of a payee after confirming the budget and payee selection.
- `YNAB_GET_SCHEDULED_TRANSACTION_BY_ID` — Get Scheduled Transaction by ID — Tool to retrieve a single scheduled transaction. Use when you need details of a specific scheduled transaction by its ID after confirming the budget.
- `YNAB_GET_TRANSACTION_BY_ID` — Get Transaction by ID — Tool to retrieve a single transaction by its ID. Use when you need detailed information for a specific transaction after confirming the budget.

## Auth

Auth schemes: `OAUTH2`. Managed by Definable: `OAUTH2` — no client credentials required from the user.

## How agents use YNAB

Inside a Definable workflow, YNAB is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → YNAB** — the Researcher (GPT-5.5) pulls context from YNAB (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → YNAB** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into YNAB (create record, post message, draft email).
- **Designer / Engineer → Distributor → YNAB** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via YNAB (attach file, open PR comment, post status).

The Verifier checks every YNAB call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- accounting — https://definable.ai/apps/category/accounting/

## Related

- HTML page: https://definable.ai/apps/ynab/
- Same category (accounting): https://definable.ai/apps/category/accounting/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt