The record, talking to the rest.
Next on the roadmap. Jobs, invoices, and customers as triggers across Zapier’s app ecosystem: the follow-up work your office retypes today, fired from the record once the integration ships.
Thorbis ↔ Zapier
- Job created / status changetrigger
- Invoice eventstrigger
- Customer lifecycletrigger
- Ordinary API calls$0
The data contract
What moves, and which way.
Events, outbound
When the integration ships, job creation and status changes, invoice events, customer updates, and schedule changes fire as triggers: the record telling the rest of your stack what happened.
Actions, in your tools
A new customer starts the welcome email in your CRM. A closed job posts the ask-for-a-review task. The week’s numbers land in a sheet without anyone exporting.
Multi-step, when earned
Filters, formatters, and branching are all available, after the first simple Zap has run for a week and someone owns its exceptions.
For developers
The API underneath is yours too.
Zapier is the no-code surface of the same API and webhooks any developer can call: documented, and never billed per call. The developer pages →
Wired, not welded
A connection you can unplug.
Every integration is a stated contract: what flows, which way, and what happens when you turn it off. No integration holds your data hostage.
The connection model
Connect. Normalize. Then automate.
01
Connect
Authorize the account and choose what moves. Admin access in both systems, granted once, visible always.
02
Normalize
External records land in their Thorbis homes: a customer is a customer, an invoice is an invoice, no bespoke shapes.
03
Automate
Only after the first records are verified by a person. The connection has an owner before it has automation.
A system of record
Every field has one home that wins. The books stay QuickBooks’s; the jobs stay Thorbis’s. Nothing is mastered in two places.
A sync owner
One named person reads the sync health and the exception queue. A connection nobody owns is an outage nobody notices.
An exception path
Records that do not match cleanly go to human review, never silently overwritten, never silently dropped.
Go-live
Staged, so the books stay clean.
01
Connect a test slice
A test account or a limited data set, never the whole company on day one.
02
Verify the mapping
Fields, permissions, and record categories checked against what you expect.
03
Run one real workflow
A single invoice, a single payment, followed to its destination and read.
04
Watch, then widen
Sync health reviewed after launch, the exception owner named, then the volume.
Asked before connecting
Straight answers.
Does automation cost extra on the Thorbis side?
No. Ordinary API calls and webhooks are $0. They are on the never-metered list. Zapier’s own plan pricing is Zapier’s; we do not resell it or mark it up.
Is there a limit on volume?
Your Zapier plan governs Zap throughput. Thorbis does not throttle beyond ordinary API rate limits, and hitting them is a conversation, not a surprise bill.
What should the first Zap be?
Something you can check by hand: closed job to review request, or new customer to the mailing list. One trigger, one action, one owner. Then grow it.
Other integrations
Start
Automate the follow-up, not the judgment.
The record fires the events; your tools do their jobs; a person still owns the exceptions. That is automation that survives an audit.
Coming from a suite? We’ll extract your records.
Rather talk first? Email the team.