# How to connect QuickBooks to Grok Bot (no API keys)

> Connect QuickBooks to Grok Bot with ClawLink in one click — 105 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.

Web version: https://claw-link.dev/grokbot/quickbooks

Grok Bot runs on its own cloud computer, so most QuickBooks guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical QuickBooks setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real QuickBooks actions from chat with no auth, token refresh, or tool wiring to build yourself.

**Start here — paste this into Grok Bot to set up ClawLink:**

> Set up ClawLink for me and tell me when it's ready.
> 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login`
> 2. I'll approve it in my browser, then reply "approved".
> 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect quickbooks`
> 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready.

## Setup

It takes three steps to connect Grok Bot to QuickBooks.

1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints.
2. **Connect QuickBooks** — `npx -y @useclawlink/cli connect quickbooks`, then approve in the browser.
3. **Use it from chat** — ask Grok Bot in plain English.

**The same CLI works from any agent with shell access:**

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect quickbooks  # connect QuickBooks (browser OAuth)
npx -y @useclawlink/cli actions quickbooks  # list available actions
npx -y @useclawlink/cli run quickbooks <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval:

```bash
npx -y @useclawlink/cli login          # prints an approval link, approve it in your browser
npx -y @useclawlink/cli connect quickbooks
```

Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI.

Verify the connection by asking Grok Bot:

> Create it in QuickBooks for me, then confirm the important fields before you finish.

### Using a different agent?

The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once QuickBooks is connected in the dashboard, that agent calls the same 105 QuickBooks tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## QuickBooks MCP for Grok Bot

Looking for a QuickBooks MCP server for Grok Bot? ClawLink connects QuickBooks to Grok Bot and exposes 105 QuickBooks tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw QuickBooks integration](https://claw-link.dev/openclaw/quickbooks) and the [Hermes QuickBooks integration](https://claw-link.dev/hermes/quickbooks) connect the same ClawLink account the same way.

## What the Grok Bot QuickBooks integration can do

105 QuickBooks tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 105.

### 30 of 105 QuickBooks tools for Grok Bot

| Tool | What it does |
|---|---|
| **Create account** `quickbooks_create_account` | Create a new account in QuickBooks |
| **Create bill** `quickbooks_create_bill` | Create a new bill in QuickBooks |
| **Create credit memo** `quickbooks_create_credit_memo` | Create a new credit memo in QuickBooks |
| **Create customer** `quickbooks_create_customer` | Create a new customer in QuickBooks |
| **Create deposit** `quickbooks_create_deposit` | Create a new deposit in QuickBooks |
| **Create employee** `quickbooks_create_employee` | Create a new employee in QuickBooks |
| **Create estimate** `quickbooks_create_estimate` | Create a new estimate in QuickBooks |
| **Create invoice** `quickbooks_create_invoice` | Create a new invoice in QuickBooks |
| **Customer balance detail** `quickbooks_customer_balance_detail` | Generate a balance detail report for a customer in QuickBooks with the given customer ID |
| **Customer balance report** `quickbooks_customer_balance_report` | Generate a customer balance report in QuickBooks showing outstanding balances for customers |
| **Get aged receivables report** `quickbooks_get_aged_receivables_report` | Generate an aged receivables report showing outstanding customer balances by age |
| **Get attachable** `quickbooks_get_attachable` | Read details of a specific attachable by ID in QuickBooks Online |
| **Get balance sheet report** `quickbooks_get_balance_sheet_report` | Generate a Balance Sheet report showing company assets, liabilities, and equity at a point in |
| **Get bank account** `quickbooks_get_bank_account` | Retrieve a specific bank account by ID from QuickBooks Payments API |
| **Get bill** `quickbooks_get_bill` | Fetch a QuickBooks bill by ID |
| **Get bill payment** `quickbooks_get_bill_payment` | Retrieve details of a specific bill payment by ID in QuickBooks Online |
| **Get changed entities** `quickbooks_get_changed_entities` | Retrieve entities that changed since a specified timestamp using QuickBooks Change Data Capture |
| **Get company info** `quickbooks_get_company_info` | Read company information from QuickBooks Online |
| **Get credit memo** `quickbooks_get_credit_memo` | Fetch a QuickBooks credit memo by ID |
| **Get credit memo PDF** `quickbooks_get_credit_memo_pdf` | Download a QuickBooks credit memo as a PDF file |
| **Get department** `quickbooks_get_department` | Read details of a specific department by ID in QuickBooks Online |
| **Get deposit** `quickbooks_get_deposit` | Read details of a specific deposit by ID in QuickBooks Online |
| **Get estimate** `quickbooks_get_estimate` | Fetch a QuickBooks estimate by ID |
| **Get estimate PDF** `quickbooks_get_estimate_pdf` | Download a QuickBooks estimate as a PDF file |
| **Get exchange rate** `quickbooks_get_exchange_rate` | Get exchange rate for a specific currency code and date in QuickBooks Online |
| **Get general ledger report** `quickbooks_get_general_ledger_report` | Generate a General Ledger report showing all transactions with debits, credits, and running |
| **Get inventory valuation summary** `quickbooks_get_inventory_valuation_summary` | Generate an Inventory Valuation Summary report showing inventory quantities and their current |
| **Get invoice PDF** `quickbooks_get_invoice_pdf` | Download a QuickBooks invoice as a PDF file |
| **Get item** `quickbooks_get_item` | Retrieve a specific item by its ID from QuickBooks Online |
| **Get journal entry** `quickbooks_get_journal_entry` | Read details of a specific QuickBooks journal entry by ID |

## Example prompts

**Create Account**

> Create it in QuickBooks for me, then confirm the important fields before you finish.

**Create Bill**

> Create it in QuickBooks for me, then confirm the important fields before you finish.

**Create Credit Memo**

> Create it in QuickBooks for me, then confirm the important fields before you finish.

**Create Customer**

> Create it in QuickBooks for me, then confirm the important fields before you finish.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want QuickBooks working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Connection flow** | Register a QuickBooks app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect QuickBooks through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for QuickBooks. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| **Agent usability** | You still need to expose the right QuickBooks actions to the runtime in a format your agent can reliably use. | 105 tools for QuickBooks are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes QuickBooks to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect QuickBooks in the browser, and the 105 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in.

### Connection succeeds but no tools appear
Reconnect QuickBooks from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

### "Tool schema not loaded yet" error when calling QuickBooks tools
QuickBooks tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every QuickBooks call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

### QuickBooks returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

### OAuth finished in the browser but the account is still missing
Try reconnecting QuickBooks and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

### Is there a Grok Bot QuickBooks integration?
Yes. ClawLink is the fastest way to connect Grok Bot to QuickBooks: link your QuickBooks account once in the browser and Grok Bot can call the QuickBooks API through 105 ready-made tools — no custom code or token handling.

### How do I connect QuickBooks to Grok Bot with ClawLink?
Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect quickbooks` to authorize QuickBooks. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage.

### How long does it take to connect QuickBooks to Grok Bot?
About two minutes. Sign in, click Connect next to QuickBooks in the dashboard, authenticate, and Grok Bot can use it from the next chat message.

### Why use ClawLink instead of wiring QuickBooks up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want QuickBooks working from chat.

### Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in.

## Related

- [Stripe](https://claw-link.dev/grokbot/stripe) — Manage payments, customers, and invoices
- [Grok Bot Zoho Books integration](https://claw-link.dev/grokbot/zoho-books) — Organize finances, invoices, bills, and accounting
- [Connect Zoho Invoice](https://claw-link.dev/grokbot/zoho-invoice) — Create and send invoices, track payments, and manage billing