How do you connect a CRM to QuickBooks?

Send the won-deal event from the CRM to Zapier, Make or n8n, and let that tool create the QuickBooks customer and invoice.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

app.salescrew.io/inbox
The unified reply inbox with classified threads

The short answer

  • You connect a CRM to QuickBooks Online with an app the CRM vendor built for it, or with Zapier, Make or n8n in the middle. The automation tool listens to the CRM's webhooks.
  • Zapier's QuickBooks Online app, Make's verified QuickBooks app and n8n's built-in QuickBooks node all create customers and invoices, as checked in September 2026.
  • Your sync should run in two directions: a won deal creates the invoice, and a paid invoice updates the deal.
  • SalesCrew connects to QuickBooks through outbound webhooks plus Zapier, Make or n8n, and takes updates back through its API and MCP tools.

Decide what each system owns before you connect them

A CRM and QuickBooks both keep a customer list, and that's where most syncs go wrong. If both systems can create customers, you'll get the same company twice with two spellings. Pick one rule and write it down.

Here's the rule that holds up: the CRM owns people and deals until a deal is won. At that moment the automation creates one QuickBooks customer and one invoice. QuickBooks then owns billing, and the CRM stores the QuickBooks customer ID so it never creates a second one.

What the automation tools can do in QuickBooks Online

Read on each tool's own QuickBooks page.

ToolQuickBooks connectorCreatesCan trigger on
ZapierQuickBooks Online app, 25+ triggers and 40+ actionsCustomer, invoice, estimate, paymentNew invoice, new payment, new paid invoice
MakeVerified QuickBooks app, 93 modulesCustomer, bill, payment, credit memo2 trigger modules
n8nBuilt-in QuickBooks Online nodeCustomer, invoice, estimate, paymentReads invoices and payments; pair with a schedule
SalesCrew (our product)Outbound webhooks plus Zapier, Make or n8nSends the won-deal event as signed JSONTakes updates back through the API and MCP tools

Connector details checked on zapier.com/apps/quickbooks, make.com/en/integrations/quickbooks and docs.n8n.io, September 2026.

Connect a won deal to a QuickBooks invoice

  1. 1

    Create the receiver

    In Zapier add a Webhooks by Zapier Catch Hook, in Make add a custom webhook, or in n8n add a Webhook node. Copy the URL it gives you.

  2. 2

    Add the webhook in the CRM

    In SalesCrew open Settings, then Webhooks, then Add. Paste the URL and tick the deal.stage_changed event. Send a test ping and check for a 200.

  3. 3

    Filter for won deals

    Add a filter step so only a move into your won stage continues. Every other stage change stops here.

  4. 4

    Find or create the customer

    Search QuickBooks for the customer first. Create a customer only when the search finds nothing, then write the QuickBooks ID back to the CRM record.

  5. 5

    Create the invoice

    Map the deal value and line items to a QuickBooks invoice. Send it from QuickBooks so payment tracking stays in one place.

How SalesCrew sends and receives the events

SalesCrew posts every event you tick as JSON, with an X-SalesCrew-Signature header you can verify. Failed deliveries retry with backoff, and the Deliveries list lets you replay one. Our setup guide, send CRM events to Zapier with webhooks, walks through each screen.

The return trip runs through the API or the MCP server. When QuickBooks reports a paid invoice, your automation can add a note to the deal or move its stage. The same tools work from Claude, ChatGPT or Cursor. See the mechanism on the Zapier integration page, or compare it with n8n.

Search before you create a QuickBooks customer

A zap that creates a customer on every won deal will duplicate any client who buys twice. Always search for the customer first, and store the QuickBooks ID on the CRM record. Cleaning up duplicate customers in your books takes far longer than adding one search step.

Questions

Can Zapier connect a CRM to QuickBooks Online?
Yes. Zapier's QuickBooks Online app lists more than 25 triggers and 40 actions, including Create Customer, Create Invoice and New Paid Invoice, as of September 2026. Point a CRM webhook at a Zapier Catch Hook, then add the QuickBooks actions you need.
Should the CRM or QuickBooks own the customer record?
Let the CRM own the customer until the deal is won, then let QuickBooks own billing. Create the QuickBooks customer once, on the won event, and store its ID on the CRM record. That one rule stops duplicate customers, which is the most common sync mess.
How do I see in my CRM when a QuickBooks invoice is paid?
Use QuickBooks as the trigger. Zapier's New Paid Invoice trigger fires when an invoice balance reaches zero, and n8n's QuickBooks node can read payments. Send that event back to the CRM through its API or MCP server to add a note or move the deal.
How does SalesCrew connect to QuickBooks?
SalesCrew connects to QuickBooks Online through outbound webhooks and an automation tool in the middle: Zapier, Make or n8n. A deal.stage_changed event is posted as signed JSON, and failed deliveries retry with backoff. The reverse direction runs through the SalesCrew API or its 140+ MCP tools.