Connect n8n and QuickBooks

In short

Connecting n8n to QuickBooks Online lets workflows read documents, match them to the books and post or report without retyping. SBD runs six fixed-scope n8n automations with QuickBooks for a US rental portfolio of around 120 properties, including mortgage statement reconciliation and owner tax summaries. Token rotation and rate limits shape the design.

The workflows

What runs between n8n and QuickBooks.

Each line is one automated workflow. It shows the event in one tool, the checks and mapping in between, the action in the other tool and who is notified.

1. Mortgage statements reconciled

   When

   A mortgage statement arrives

   Automation

   • Verify and validate
   • Map and normalise
   • Upsert by key

   Then

   Read it, match it to the property and reconcile it against what is recorded in QuickBooks

   And

   • Audit log entry
   • Alert if it fails or goes quiet
   • Review queue if unsure

2. Owner tax summaries at year end

   When

   Year end

   Automation

   • Verify and validate
   • Map and normalise
   • Upsert by key

   Then

   Generate a tax summary per owner from the QuickBooks records

   And

   • Audit log entry
   • Alert if it fails or goes quiet
   • Review queue if unsure

3. Utility and maintenance bills posted

   When

   A utility or maintenance bill is received

   Automation

   • Verify and validate
   • Map and normalise
   • Upsert by key

   Then

   Create the bill in QuickBooks against the right vendor and property

   And

   • Audit log entry
   • Alert if it fails or goes quiet
   • Review queue if unsure

4. Failures and doubtful matches reviewed

   When

   Any workflow fails or a match is uncertain

   Automation

   • Verify and validate
   • Map and normalise
   • Upsert by key

   Then

   Run the error workflow, alert a named person and queue the item for review

   And

   • Audit log entry
   • Alert if it fails or goes quiet
   • Review queue if unsure

Every record passes through the same stages

1. 1Receive

   Webhook or polling from the source tool, with a signed payload and a replay log.

2. 2Validate

   We check required fields, types and the record key. Anything that fails goes to the review queue.

3. 3Map

   Fields are mapped to the destination schema, with dropdown values, currencies and dates normalised.

4. 4Upsert

   Each write is matched on the record key, so a retry updates the existing record.

5. 5Confirm

   The outcome is logged, an alert fires if the count stops moving, and a reconciliation runs each night.

Read this first

Where the simple setup breaks down.

A one-step Zap connects n8n and QuickBooks in an afternoon. This is what tends to go wrong once volume grows and edge cases appear.

• The refresh token changes as you use it

  QuickBooks access tokens last one hour. When a new refresh token is issued, Intuit expires the previous value, so the integration must store the newest one every time. Two tools sharing one QuickBooks connection will invalidate each other, and the books stop syncing without an obvious error.

• The n8n node does not cover every object

  The built-in QuickBooks Online node handles bills, customers, employees, estimates, invoices, items, payments, purchases, vendors and a transaction report. Anything outside that list goes through the HTTP Request node using the same QuickBooks credential, which needs the same care with errors as the node itself.

• Throttling is per company and app

  Intuit throttles at 500 requests a minute and 10 a second per company and app, and batch calls have their own lower limit. A backfill or month-end run that loops record by record gets 429 errors, and Intuit advises waiting 60 seconds before retrying.

• A failed run is silent unless you wire the alert

  n8n only runs an error workflow if one is set in the workflow settings, and that workflow must start with the Error Trigger. Without it, a reconciliation that failed on the third statement looks the same as one that finished.

What it costs today

The problem from the team's side and the technical side.

What we wire up

The data flows.

1. 01
   When

   A mortgage statement arrives

   Then

   Read it, match it to the property and reconcile it against what is recorded in QuickBooks

2. 02
   When

   Year end

   Then

   Generate a tax summary per owner from the QuickBooks records

3. 03
   When

   A utility or maintenance bill is received

   Then

   Create the bill in QuickBooks against the right vendor and property

4. 04
   When

   Any workflow fails or a match is uncertain

   Then

   Run the error workflow, alert a named person and queue the item for review

Data map

Which fields map to which, and what each one matches on.

Field-level mapping is agreed in the blueprint and written into the runbook. Two-way rows carry loop protection so a write from the sync never re-triggers the sync.

In every build

What every integration build includes.

Security and your data

Where the data goes, and who holds the keys.

Accounts

Every platform account is created in your name. We work through managed access you can revoke.

Credentials

Stored encrypted in the orchestration layer, scoped per connection and rotated at handover.

Data in transit

All traffic uses TLS, and webhooks are checked by signature before anything is processed.

Data at rest

We store only what the sync needs and keep no copies of your customer data on our machines.

AI steps

Where an integration uses a model, it is through a business API that does not train on your data.

Retention

Run logs are kept 90 days by default, which you can change. Card and ID numbers are redacted from payloads.

Agreements

DPA and NDA on request. Regional rules covered in our privacy policy.

Keys and sensitive data

How API keys, tokens and personal data are handled.

• Keys are kept in a vault

  API keys and tokens are stored in the orchestration layer's encrypted credential store or the platform's secret manager. None are written into workflows, repos, spreadsheets or chat.

• One credential per connection

  Each integration gets its own key, scoped to the objects and actions it needs. A lead sync cannot read invoices. Revoking one key stops one thing.

• Service accounts for connections

  Connections use a dedicated service user in your account, so nothing breaks when a person leaves and nothing runs under someone's name.

• Two-factor on every account

  Each platform account we set up has two-factor authentication on, and the recovery codes are handed to you.

• Rotation on handover and on request

  Keys are rotated when the build is handed over, when anyone with access leaves, and at any time you ask.

• Secrets are redacted from logs

  Audit logs redact tokens, card numbers, government IDs and anything you flag as sensitive before a line is written.

• Webhooks verified before processing

  Inbound calls are checked against the sending tool's signature. Unsigned or stale payloads are dropped and counted.

• Access you can see and revoke

  Our access is through managed roles in your accounts. You can see it, limit it or remove it without touching the build.

Engineering decisions

Decisions we make before writing the first workflow.

• Rate limits and backoff

  Each API has a ceiling, so calls are batched, queued and retried with increasing delays during busy periods.

• Backfill and pagination

  The first run loads history as well as new events. Backfills page through the source in order and resume after an interruption without writing a record twice.

• Out-of-order and duplicate events

  Webhooks can arrive twice or out of sequence. Each event carries a version or timestamp, so an older version cannot overwrite a newer one.

• Schema changes

  A renamed field or a new dropdown value is a common cause of silent failure. Payloads are checked against a contract, and a mismatch stops the run and raises a flag.

• Time zones, currencies, units

  Dates are stored in UTC and shown in local time. Amounts carry their currency and quantities their unit, and conversions happen once, in the map step.

• Sandbox first

  Builds run against sandbox or test accounts with seeded data first. Going live means switching credentials.

• Versioned and reversible

  Workflows and code are version-controlled. A release can be rolled back in minutes without losing the records processed since.

• API deprecations watched

  Tools retire API versions on a schedule. We track the dates for every connection in the runbook and upgrade before the cut-off.

• Cost per run known

  Each run logs its cost, including any model calls, so you can see spend as it builds up.

• Run metrics

  We chart runs per hour, records in and out, exception rate and latency, which often shows a problem before an alert fires.

Proof

Where we have done this.

• Customer story

  Property operations automations and agent fleet

  Six fixed-scope n8n automations for a US rental portfolio of around 120 properties, including mortgage reconciliation and owner tax summaries, with QuickBooks in the stack.

  Read the story →

Questions

What people ask about this pair.

Related

• +

  Shopify and QuickBooks

  Sales, fees and refunds posted so the books match each payout.

• +

  Zoho Books and Airtable

  Invoice from the event that earned it, and see what is outstanding without opening Books.

• +

  Tally and Airtable

  Tally stays the book of record, and your team can see what is in it without asking accounts.

• Solution

  Real estate

  The workflows we automate for this kind of team.