Integration · Payments and finance
AI agents for YNAB
Read YNAB (You Need A Budget) plans, accounts, categories, monthly budgets and transactions, add, edit and delete transactions, and assign money to a category for a month, with a YNAB personal access token.
- Actions
- 10
- Read
- 6
- Write
- 4
Actions
What your agents can do in YNAB
10 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 6
Look things up. Nothing changes.
Get the user
Reads the YNAB user the token belongs to (data.user.id).
List plans (budgets)
Lists the user's plans (what YNAB used to call budgets): each with id, name, last_modified_on, first_month, last_month and currency_format, plus default_plan.
List accounts
Lists a plan's accounts (checking, savings, credit cards, loans, tracking).
List categories
Lists a plan's category groups and their categories for the current month.
Get a budget month
Reads one month of a plan: income, budgeted, activity, to_be_budgeted (Ready to Assign) and age_of_money, and every category's assigned, spent and available amounts for that month.
List transactions
Lists a plan's transactions from a date on (and up to an end date), or only the uncategorized or unapproved ones.
Write 4
Create, change or send.
Add a transaction
Adds a transaction to an account: date (today or earlier), amount in milliunits (negative for spending, like -12500 for 12.50 out; positive for income), and a payee by id or by name.
Edit a transaction
Changes an existing transaction by id: its date, amount, payee, category, memo, cleared status, approval or flag.
Delete a transactionDeletes data
Deletes a transaction by id.
Assign money to a category
Sets how much is assigned (budgeted) to a category in a month, in milliunits (like 400000 for 400.00).
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your YNAB account.
What you enter
- Personal access token
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your YNAB data
Ask a question in plain words. The agent can get the user, list plans (budgets) or list accounts in YNAB, then answers with what it found.
- 02
Let an agent update YNAB
Have the agent add a transaction or assign money to a category in YNAB as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent YNAB and Slack: it can get the user in YNAB and post a summary to a Slack channel in the same run.
FAQ
YNAB and MyDeepAgents
Can MyDeepAgents connect to YNAB?
Yes. The YNAB connector has 10 actions: 6 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect YNAB?
Paste an API key from your YNAB account. You'll need: Personal access token. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in YNAB without asking?
Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use YNAB in workflows as well as agents?
Yes. Every YNAB action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put YNAB to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.