QuickBooks Desktop
integration for apps
and AI tools

Conductor connects QuickBooks Desktop to your code through Python, Node.js, and REST, and to Claude, ChatGPT, and other AI tools through MCP. Set it up once, then read and write your QuickBooks data in real time.

Get started >

Explore the docs >

SYNCING 1,800+ BUSINESSES

M
Miter
Pallet
SilkRoute AI
WizCommerce
Attain
CLOUDRIG

munch insights
DEV///AO

Every record,
every report

Conductor’s QuickBooks Desktop API covers the whole company file: customers, vendors, employees, items and inventory, invoices, bills, payments, journal entries, and reports.

Your code or AI tool can look up, create, and update any record and delete any transaction, through typed SDKs for Python and Node.js, plain REST, or MCP.

npm install conductor-node

pip install conductor-py

import Conductor from "conductor-node";
const conductor = new Conductor({ apiKey: "sk_test_..." });

// Create, fetch, or update any QuickBooks Desktop object.

const invoice = await conductor.qbd.invoices.create({

conductorEndUserId: "end_usr_...",

customerId: "abc_123...",

dueDate: "2027-06-30",

lines: [{

itemId: "xyz_456...",

quantity: 5,

rate: "100.00",

}],

});

Every connection
at a glance

The Conductor dashboard lists every QuickBooks Desktop connection with its company file, whether it is online, and when QuickBooks last checked in. When a connection stops syncing, you can test it with one click or reset a moved company file from the same page.

Guided setup,
start to finish

Conductor connects through the QuickBooks Web Connector, Intuit’s own tool for linking QuickBooks Desktop to other software. Setup walks you through each step on the Windows computer that runs QuickBooks:

Each screen shows what to click in QuickBooks and the Web Connector, from download to a working connection.

Step-by-step help guides cover the Windows and QuickBooks problems that can block a connection.

At the end, Conductor checks the connection and tells you what to fix if the check fails.

Errors that
say what to do

Raw QuickBooks Desktop errors are often a bare code or a message with no next step. Conductor rewrites each one to say what went wrong and how to fix it, with a link to a step-by-step guide when one exists.

Real QuickBooks Desktop errors

Error from QuickBooks DesktopNo next step

Retrieving the COM class factory for component with CLSID {45F5708E-3B43-4FA8-BE7E-A5F1849214CB} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

Improved error from Conductor

QuickBooks Desktop connection failed (0x80040154): We could not connect to your QuickBooks Desktop because some QuickBooks integration components on your computer are not set up correctly. This usually happens after a QuickBooks installation or update issue. To fix this, follow this guide to re-register the QuickBooks components: https://docs.conductor.is/help/connection-errors/unable-to-cast-com-object

Error from QuickBooks DesktopJust the code

Exception from HRESULT: 0x80040414

Improved error from Conductor

QuickBooks Desktop connection failed (0x80040414): We could not connect to your QuickBooks Desktop because QuickBooks is waiting for input on a pop-up or modal window. To fix this, bring QuickBooks to the foreground on the sync computer, close or respond to all open dialogs (including any hidden behind other windows), then try again. If the issue persists, close QuickBooks Desktop completely, reopen the company file, and retry.

Error from QuickBooks DesktopDoesn't say which

The specified parameters conflict with each other.

Improved error from Conductor

QuickBooks Desktop error (3153): The specified parameters conflict with each other. QuickBooks does not say which, but the known causes are a line that sets both `itemId` and `linkToTransactionLine` (omit `itemId`; the linked line supplies the item), or a vendor or customer that differs from the one on the linked transaction, such as a purchase order.

Error from QuickBooks DesktopNo message

statusMessage:

QuickBooks Desktop returns no message for this error.

Improved error from Conductor

QuickBooks Desktop error (3415): Sales tax code preference mismatch. Your request includes a tax code or sales-tax value that conflicts with the QuickBooks company file's setting 'Use Customer/Vendor Tax Codes'. Either enable or disable that QuickBooks preference to match your request, or remove the tax fields from your request, then retry.

Frequently asked questions

Does QuickBooks Desktop have an API?

Not a web API. Intuit’s QuickBooks Desktop SDK only talks to QuickBooks on the same Windows computer, and other software reaches it through the QuickBooks Web Connector. Conductor runs that connection for you and adds a REST API, Python and Node.js SDKs, and an MCP server.

Which versions of QuickBooks Desktop does Conductor support?

Conductor supports QuickBooks Enterprise in any version, and QuickBooks Pro, Premier, and Accountant from 2018 on, including every industry edition. QuickBooks Desktop for Mac does not work because it has no Web Connector.

Does QuickBooks Desktop need to stay open?

Yes. The computer with QuickBooks Desktop must be on, with QuickBooks Desktop and the Web Connector running. QuickBooks can wait at the “No Company Open” screen; it opens the company file for each sync.

Can I connect QuickBooks Desktop to Claude or ChatGPT?

Yes. Add Conductor’s MCP server at mcp.conductor.is to Claude, ChatGPT, Cursor, or another AI tool and sign in to Conductor when it asks. The AI tool can then look up, create, and update your QuickBooks Desktop data.

Does Conductor work with hosted QuickBooks Desktop?

Yes. Conductor works with hosting providers such as Rightworks, Summit Hosting, and Cloud9. On Rightworks, you need to stay signed in to your remote desktop session while QuickBooks syncs.