QuickBooks
Manage QuickBooks Online customers, invoices, items, vendors, payments, bills, accounts and reports.
About
QuickBooks ships in the w6w first-party pack. It declares 20 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.quickbooks- Version
- 0.1.4
- Author
- w6w
- Licence
- MIT
- Categories
- Finance & Accounting
Overview
QuickBooks Online is where a lot of small-business accounting actually happens, and this app puts the core of it under workflow control: customers, invoices, items, vendors, payments, bills and the chart of accounts, plus a Profit and Loss report and a raw query action for anything else in the ledger.
Creating and updating these records follows QuickBooks’ own rules rather than assuming a generic REST shape: updates require the record’s current version token and apply only the fields a workflow actually supplied, so two processes editing the same invoice can’t silently overwrite each other’s changes. The raw query action is there deliberately, covering entities like journal entries or tax codes that don’t have a dedicated action of their own, so a workflow isn’t blocked on waiting for one to be added.
Employees, purchase orders, deposits, and operations like voiding a transaction or emailing a PDF invoice are left out of this first pass — most of what they’d need is still reachable read-only through the same raw query action, which is exactly the escape hatch it’s there for.
Build with QuickBooks
Three routes to the same 20 actions. The Workflow tab is generated from QuickBooks's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Run Query
query Run a raw QuickBooks query-language statement against any entity — the escape hatch for resources this app has no dedicated action for (CreditMemo, JournalEntry, TaxCode, Deposit, …).
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying QuickBooks's real ids.
{
"manifestVersion": "2",
"name": "quickbooks-example",
"steps": [
{
"id": "bill-create",
"uses": {
"app": "io.w6w.quickbooks",
"action": "bill-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"vendorId": "<vendorId>",
"lines": "<lines>"
}
}
]
}Here are some of the things you can do
-
Create Bill
performbill-create -
List Accounts
readaccount-list -
List Bills
readbill-list -
Create Customer
performcustomer-create -
Get Customer
readcustomer-get
+15 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for QuickBooks, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to QuickBooks. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "invoice-create",
payload: {
customerId: "<value>",
lines: "<value>",
// additionalFields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action invoice-create --payload '{"customerId":"<value>","lines":"<value>"}'Give an AI agent QuickBooks — without giving it QuickBooks's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.quickbooks#bill-create",
"input": {
"vendorId": "<vendorId>",
"lines": "<lines>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's QuickBooks connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
QuickBooks's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. QuickBooks itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
QuickBooks declares its own checks, so its health is a property of the app rather than something the host guesses at.
QuickBooks Online platform status
Atlassian Statuspage rollup for status.developer.intuit.com, with per-component detail. Unauthenticated and unsigned.