QuickBooks Desktop (via Conductor)

Sync invoices, bills, customers, vendors and payments with QuickBooks Desktop through the Conductor API bridge.
Connect it
In Keystile Automations → Connections → New connection, choose QuickBooks Desktop (via Conductor) and sign in. Your AI tools and workflows then use it through Keystile; they never see the password or key.How connecting works.
Try it from your AI tool
Using Keystile, in QuickBooks Desktop (via Conductor): list items (Lists Service and Non-Inventory items from QuickBooks Desktop, for finding the exact item name to use in Create Invoice's line items).What it can do (8 actions)
| Action | What it does | Changes data |
|---|---|---|
| Create Bill | Creates a vendor bill (accounts payable) in QuickBooks Desktop, expensed against one or more accounts. | Yes |
| Create Invoice | Creates an invoice for a customer in QuickBooks Desktop. | Yes |
| Custom API Call | Make a custom API call to a specific endpoint | Yes |
| List Items | Lists Service and Non-Inventory items from QuickBooks Desktop, for finding the exact item name to use in Create Invoice's line items. | |
| Query Transactions | Searches across all transaction types in QuickBooks Desktop (invoices, bills, payments, and more) with date and type filters. | |
| Record Payment | Records a customer payment against open invoices, or a vendor bill payment by check or credit card, in QuickBooks Desktop. | Yes |
| Upsert Customer | Creates a customer in QuickBooks Desktop, or updates it if one with the same name already exists. | Yes |
| Upsert Vendor | Creates a vendor in QuickBooks Desktop, or updates it if one with the same name already exists. | Yes |
Start a workflow when… (2 triggers)
- New or Updated Invoice — Fires when an invoice is created or updated (e.g. line items, balance, or payment status changed) in QuickBooks Desktop. One event per invoice change, not create-only.
- New Payment — Fires once when a new customer payment is recorded (Accounts Receivable) in QuickBooks Desktop — a "Receive Payment" transaction, e.g. from the Record Payment action's Customer Payment mode. Create-only: editing an existing payment does not re-fire it. Vendor bill payments (Accounts Payable) do not fire this trigger.
How Keystile protects it
Every QuickBooks Desktop (via Conductor) action is checked before it runs, whether it comes from an AI tool or a workflow. 6 of its actions change data; your rules, limits and budgets decide whether each is allowed, held for a person or stopped, and it all goes into the signed record.
Use QuickBooks Desktop (via Conductor) with your AI assistant — safelyClaude, Cursor or ChatGPT do the work; Keystile checks every action first.
Get early access