Can the destination be something other than a CRM?

Yes. The last step is a plain HTTP request, so any system with a create endpoint works: a Postgres table through Supabase, an internal tool, a helpdesk. The guide shows three request bodies and you edit the mapping table for anything else.

What happens if the destination rejects a record?

The run stops with the error and the customer that caused it. n8n keeps the failed execution for you to retry once the field is fixed, and the high-water mark only advances after a successful run. Nothing is skipped.

Does it update customers that change later in QuickBooks?

Not in this package. It handles creation only, which is the part people retype. Updates need a second query on LastUpdatedTime and a match on the stored ID; that is a small change and the guide points to where it goes.

Will this work on Make or Zapier?

Both have a polling trigger for new QuickBooks customers and an HTTP module, so the same four steps rebuild in either. Zapier's Webhooks app is a premium app, so it needs a paid Zapier plan. The package ships the n8n export plus a step list for the other two, not native Make or Zapier files.

QB{}In build

Data sync & backups

New QuickBooks Online customer → record created in any app with an API

Add a customer in QuickBooks once; the same record lands in your CRM by API.

Every customer added to QuickBooks Online is created in your CRM or job system by API, without anyone retyping it. The workflow checks QuickBooks every 15 minutes. Name, email, phone, billing address and open balance are mapped to the destination's field names, then the record is posted. Any app with a create endpoint can be the destination: HubSpot, Pipedrive, a Postgres table, an in-house tool.

How it works

QB
Trigger
New customer created (checked every 15 minutes through the QuickBooks Online API)
QuickBooks Online
QB
Step 1
Pull customers created since the last run
Runs a Customer query filtered on MetaData.CreateTime and returns Id, DisplayName, CompanyName, GivenName, FamilyName, PrimaryEmailAddr, PrimaryPhone, Mobile, BillAddr, Balance and Active for each customer added since the last run.
if
Step 2
Map QuickBooks fields to the destination's schema
Renames each QuickBooks field to what the destination expects: first and last name from GivenName and FamilyName, one phone from PrimaryPhone or Mobile, and the billing address as four separate parts. The mapping lives in one editable table.
{}
Step 3
Create the record with an HTTP POST
Sends the mapped JSON to the destination's create endpoint with its API key in the header, then keeps the returned record ID and HTTP status.
if
Step 4
Advance the high-water mark
Stores the newest CreateTime from this run in the workflow's static data, so the next run fetches only customers added after it. Nothing is created twice.

What changes once it runs

Within 15 minutes of being created in QuickBooks, the customer exists in the destination.
Name, company, email, phone, billing address and open balance arrive in the destination's own field names.
Customers are created once. The stored high-water mark stops re-sends after a restart.
The QuickBooks customer ID travels with the record, so later matching is by ID rather than by name.

What you get

The n8n workflow export, tested against a QuickBooks sandbox company
A first-run mode that pushes every existing customer once, with the date filter switched off
Setup guide covering the Intuit developer app, the OAuth2 connection and the destination's API key
Field-mapping sheet with the QuickBooks customer fields pre-filled on one side
Worked request bodies for HubSpot, Pipedrive and a Supabase REST endpoint
Recorded walkthrough of the first run, plus 30 days of email support

Before you start

QuickBooks Online on any plan (QuickBooks Desktop is not supported) with an Intuit developer app connected to n8n by OAuth2
A destination app with a documented create endpoint and an API key or token you can issue
n8n Cloud, or the free self-hosted community edition; the QuickBooks and HTTP Request nodes are built in
Your list of which QuickBooks fields map to which destination fields (a template is included)

Built for

Questions before you buy

Can the destination be something other than a CRM?: Yes. The last step is a plain HTTP request, so any system with a create endpoint works: a Postgres table through Supabase, an internal tool, a helpdesk. The guide shows three request bodies and you edit the mapping table for anything else.
What happens if the destination rejects a record?: The run stops with the error and the customer that caused it. n8n keeps the failed execution for you to retry once the field is fixed, and the high-water mark only advances after a successful run. Nothing is skipped.
Does it update customers that change later in QuickBooks?: Not in this package. It handles creation only, which is the part people retype. Updates need a second query on LastUpdatedTime and a match on the stored ID; that is a small change and the guide points to where it goes.
Will this work on Make or Zapier?: Both have a polling trigger for new QuickBooks customers and an HTTP module, so the same four steps rebuild in either. Zapier's Webhooks app is a premium app, so it needs a paid Zapier plan. The package ships the n8n export plus a step list for the other two, not native Make or Zapier files.

Nearby on the shelf

Whole catalog