YNAB

CRM and sales

YNAB for AI agents. Managed auth, ready-made tools.

Read budgets, accounts and categories, and add or update transactions in YNAB on behalf of each of your users.

About YNAB

With the YNAB connector, your agent works with each user’s own YNAB budgets. It can list budgets, accounts and categories, read a month’s budget, list transactions and add or update a transaction, using only the tools your project allows.

YNAB, short for You Need A Budget, is a personal budgeting app.

Tools

What your agent can do in YNAB.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own YNAB connection.

  • List budgets

    Read
    ynab_list_budgets

    List the user's budgets.

  • List accounts

    Read
    ynab_list_accounts

    List the accounts in a budget and their balances.

  • List categories

    Read
    ynab_list_categories

    List categories with budgeted and available amounts.

  • Get a month

    Read
    ynab_get_month

    Read the budget summary for a month.

  • List transactions

    Read
    ynab_list_transactions

    List transactions in a budget or account.

  • Create a transaction

    Write
    ynab_create_transaction

    Add a transaction to an account.

  • Update a transaction

    Write
    ynab_update_transaction

    Change a transaction's amount, category or memo.

Control

Limits you can set.

You decide what your agent may do in YNAB, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent read budgets and add transactions, and switch off ynab_update_transaction so it can never change an existing one.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example read-only access to budgets. A call outside them is refused.

Get started

Connect YNAB
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect YNAB

    Each end user authorizes their own YNAB account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own YNAB account, once.
    const connection = await agent200
      .user("user_123")
      .connect("ynab");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the YNAB tools

    Name the user, the model and the tools. The model decides which YNAB tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "How much is left in my groceries category this month",
        tools: ["ynab"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, on YNAB's own sign-in page. You never see or store their YNAB password.

  • What access is requested

    The access the connection needs, such as full or read-only access to their budgets, listed on YNAB's authorization screen. Users can remove the app later from their YNAB account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the YNAB connector and how to use it.

Agent brief
Connector: YNAB, through Agent200. In code: "ynab".
What it does: Read budgets, accounts and categories, and add or update transactions in YNAB on behalf of each of your users.
Page: https://www.agent200.com/connectors/ynab/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on YNAB's own page, through the authorization link Agent200 returns. Never ask a user for a YNAB password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: ynab_list_budgets, ynab_list_accounts, ynab_list_categories, ynab_get_month, ynab_list_transactions. Write tools: ynab_create_transaction, ynab_update_transaction. Name "ynab" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/ynab/framework/claude/
   https://www.agent200.com/connectors/ynab/framework/chatgpt/
   https://www.agent200.com/connectors/ynab/framework/claude-code/
   https://www.agent200.com/connectors/ynab/framework/muse/
   https://www.agent200.com/connectors/ynab/framework/grok-bot/
   https://www.agent200.com/connectors/ynab/framework/openai-dots/
   https://www.agent200.com/connectors/ynab/framework/claude-duet/
   https://www.agent200.com/connectors/ynab/framework/hermes-agent/
   https://www.agent200.com/connectors/ynab/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/ynab.md

Guides

Use YNAB with the AI you build on.

Step-by-step setup for YNAB with a specific model, assistant or agent framework.

FAQ

YNAB and Agent200, answered.

Who handles the YNAB OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for YNAB.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's YNAB connection, never another user's. It cannot reach anything the user or YNAB has not authorized.

Can I limit what my agent can do in YNAB?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • HubSpot

    HubSpot

    Look up and update contacts, companies and deals in your users' HubSpot CRM.

    Managed OAuth CRM and sales
  • Salesforce

    Salesforce

    Query and update accounts, contacts and opportunities in Salesforce.

    Managed OAuth CRM and sales
  • LinkedIn

    LinkedIn

    Share posts and read profile details on LinkedIn on behalf of each of your users, where the relevant API permissions are available.

    Managed OAuth CRM and sales
  • Zendesk

    Zendesk

    Search, read, create and update Zendesk tickets, and reply to customers, on behalf of each of your users.

    Managed OAuth CRM and sales
200 OK

Start with YNAB.
Your agent does the rest.

Your users connect their own YNAB accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)