CRM and sales
QuickBooks for AI agents.
Managed auth, ready-made tools.
Find and add customers, create and send invoices and pull financial reports in QuickBooks on behalf of each of your users.
About QuickBooks
With the QuickBooks connector, your agent works in each user’s own QuickBooks Online company. It can find and add customers, create and send invoices, check what is unpaid and pull reports such as profit and loss, using only the tools your project allows.
QuickBooks is Intuit’s accounting software for small businesses.
Tools
What your agent can do in QuickBooks.
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 QuickBooks connection.
-
List customers
Readquickbooks_list_customersList and search customers.
-
Create a customer
Writequickbooks_create_customerAdd a customer with a name and email.
-
List invoices
Readquickbooks_list_invoicesList invoices and their balance due.
-
Create an invoice
Writequickbooks_create_invoiceCreate an invoice for a customer with line items.
-
Send an invoice
Writequickbooks_send_invoiceEmail an invoice to the customer.
-
Run a report
Readquickbooks_get_reportGet a report such as profit and loss or balance sheet.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in QuickBooks, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read and create invoices, and switch off
quickbooks_send_invoiceso it can never email one to a customer. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example reports but not invoices. A call outside them is refused.
Get started
Connect QuickBooks
in three steps.
-
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.jsConceptual exampleSet 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
Let your user connect QuickBooks
Each end user authorizes their own QuickBooks account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own QuickBooks account, once. const connection = await agent200 .user("user_123") .connect("quickbooks"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the QuickBooks tools
Name the user, the model and the tools. The model decides which QuickBooks tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Which invoices are overdue", tools: ["quickbooks"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Intuit's own sign-in page. You never see or store their Intuit password.
-
What access is requested
The scopes the connection needs, such as accounting access to their QuickBooks company, listed on Intuit's authorization screen. Users can remove the app later from their Intuit 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 QuickBooks connector and how to use it.
Connector: QuickBooks, through Agent200. In code: "quickbooks". What it does: Find and add customers, create and send invoices and pull financial reports in QuickBooks on behalf of each of your users. Page: https://www.agent200.com/connectors/quickbooks/ 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 QuickBooks's own page, through the authorization link Agent200 returns. Never ask a user for a QuickBooks 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: quickbooks_list_customers, quickbooks_list_invoices, quickbooks_get_report. Write tools: quickbooks_create_customer, quickbooks_create_invoice, quickbooks_send_invoice. Name "quickbooks" 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/quickbooks/framework/claude/ https://www.agent200.com/connectors/quickbooks/framework/chatgpt/ https://www.agent200.com/connectors/quickbooks/framework/claude-code/ https://www.agent200.com/connectors/quickbooks/framework/muse/ https://www.agent200.com/connectors/quickbooks/framework/grok-bot/ https://www.agent200.com/connectors/quickbooks/framework/openai-dots/ https://www.agent200.com/connectors/quickbooks/framework/claude-duet/ https://www.agent200.com/connectors/quickbooks/framework/hermes-agent/ https://www.agent200.com/connectors/quickbooks/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/quickbooks.md
Guides
Use QuickBooks with the AI you build on.
Step-by-step setup for QuickBooks with a specific model, assistant or agent framework.
-
QuickBooks + Claude
How to connect QuickBooks to Claude
-
QuickBooks + ChatGPT
How to connect QuickBooks to ChatGPT
-
QuickBooks + Claude Code
How to connect QuickBooks to Claude Code
-
QuickBooks + Muse
How to connect QuickBooks to Muse
-
QuickBooks + Grok Bot
How to connect QuickBooks to Grok Bot
-
QuickBooks + OpenAI Dots
How to connect QuickBooks to OpenAI Dots
-
QuickBooks + Claude Duet
How to connect QuickBooks to Claude Duet
-
QuickBooks + Hermes Agent
How to connect QuickBooks to Hermes Agent
-
QuickBooks + OpenClaw
How to connect QuickBooks to OpenClaw
FAQ
QuickBooks and Agent200, answered.
Who handles the QuickBooks 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 QuickBooks.
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 QuickBooks connection, never another user's. It cannot reach anything the user or QuickBooks has not authorized.
Can I limit what my agent can do in QuickBooks?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.