Jobber Integrations: The Honest Guide to What Connects and What's Gated

Search “Jobber integrations” and you get Jobber’s own marketplace, Zapier’s “connect Jobber to 9,000 apps” page, and a stack of directory listings. What none of them tell you: “integration” means three very different things in Jobber, and the one most owners want sits behind the most expensive plan.

We build custom integrations for home-services businesses on Jobber, Housecall Pro, ServiceTitan, and CompanyCam. This is the guide we wish existed before every discovery call: what each tier of integration can do, what it costs, and where it breaks.

The three tiers of “Jobber integration”

That third row is the part the marketplace page doesn’t lead with, so let’s start there.

The API paywall, and this week’s price increase

Custom integrations require the Plus plan. As of our check on August 1, 2026, Plus runs $399/mo (5 users), $449/mo (10 users), or $529/mo (15 users) billed annually, and $499 to $699 month-to-month. Extra users are $29/mo on every plan.

Here’s why the verification date matters more than usual: those numbers are new this week. When we verified Jobber’s pricing on July 25, 2026, the 5-user Plus config was $280/mo annual. On August 1 the same config shows $399. That’s the second quiet pricing change we’ve caught at Jobber this summer; in May, plans were still flat-priced with fixed seat counts. No announcement either time.

Two takeaways. If you budgeted a custom integration around the old Plus price, redo the math before you commit. And if you’re reading any Jobber pricing content without a verification date, assume it’s wrong. Our full Jobber pricing breakdown covers the plan structure in detail; note it was verified against the July rates and the sticker numbers have since moved up.

What the gate means in practice: a 10-user shop on Grow at $299/mo that wants one custom integration has to move to Plus at $449/mo. That’s $1,800 more per year before a single line of integration code exists. Housecall Pro does the same thing with its MAX plan, so Jobber isn’t unusual here. Put the upgrade in your plan comparison as its own line item, because no vendor pricing page leads with it.

Tier 1: Marketplace apps, and what a listing means

Jobber’s app marketplace is real, but a listing is not a promise of depth. How the listings sort in practice:

Solid: QuickBooks Online (the most-searched Jobber integration, and the most misunderstood; more below), Gusto for payroll, Jobber Payments, Mailchimp for basic campaigns.

Fine for what they are: review-request tools, phone systems with caller-ID lookup, marketing add-ons. They do one narrow thing.

Where owners get burned: assuming a marketplace listing means deep two-way sync. Most listings are one-directional pushes built on the same plumbing Zapier uses. The test question for any app: “when data changes in the other system, does Jobber update?” Usually the answer is no.

The QuickBooks reality

QuickBooks sync is available below Plus and works for the core loop: customers, invoices, payments flow from Jobber to QuickBooks. The gotchas we clean up most often:

• Duplicate customers. If your QuickBooks file has years of history, name mismatches create doubles fast. Merge and map before enabling sync, not after.
• It’s not accounting advice. Sync timing can put payments in odd periods. Your bookkeeper should review the first two closes after turning it on.
• Line-item detail varies. Custom quote structures don’t always land in QuickBooks the way your accountant wants them categorized.

None of that is a reason to skip the sync. Just schedule a cleanup hour in week one instead of month six.

Tier 2: Zapier, honestly

Zapier’s Jobber page advertises thousands of app connections, and for trigger-action automation it delivers: job closed, post to Slack. New client, add to your email list. Invoice paid, log it in a sheet.

What Zapier cannot give you, no matter how many Zaps you stack:

• Answers. “Which crews are open Thursday?” is a query against live data. Zapier reacts to events; it doesn’t answer questions.
• True two-way sync. Bidirectional Zaps exist on paper and break in practice; conflict resolution isn’t what trigger-action tools are for.
• Bulk operations. Re-pricing 400 line items or importing a customer list is API work.

Cost also stacks quietly. Each workflow is a Zap, complex shops end up with a dozen, and the Zapier bill lands at $50-$100/mo on top of Jobber. At that point you’re paying real money for automation that still can’t answer a question. That’s usually the moment owners call someone like us, and sometimes the honest answer is “your Zaps are fine, keep them.” The other times, it’s tier three.

Tier 3: Custom API integration

This is where the things owners actually ask for live: a reporting dashboard the owner checks from a truck, a crew-availability calendar Jobber’s own scheduler can’t show, a customer portal, a connection between Jobber and software it has never heard of, or an AI assistant that can answer questions from your Jobber data.

Three build realities we’ve learned the hard way, which no vendor blog writes down:

1. Admin authorization is mandatory. Jobber doesn’t let non-admin accounts authorize API access. Every integration routes through an admin approval, so access control for your team happens inside the integration, not inside Jobber. For one client we solved this with a team password pattern: sales reps don’t get the owner’s Jobber access; they log into the integration, which holds a scoped connection to the account. Reps see availability and book jobs. They can’t see financials. Jobber’s permission model alone can’t produce that split.

2. Throttling shapes the architecture. Jobber rate-limits API requests. An integration that naively hammers the API will get slowed to a crawl on a busy Monday morning. Real integrations batch queries and cache what doesn’t need to be live. We measured the exact numbers, including what one real dashboard load costs against the budget, in Jobber API rate limits: what you can actually build.

3. The API is GraphQL, and it’s good. Credit where due: once you’re through the gate, Jobber’s API is well-documented and complete. The constraint is the gate, not the technology.

Which tier do you actually need?

• You want notifications and simple handoffs: Zapier. Don’t let anyone sell you a custom build for “post new jobs to Slack.”
• You want QuickBooks, payroll, reviews: marketplace apps. Budget a cleanup pass for the QuickBooks sync.
• You want answers, dashboards, portals, two-way sync, or anything Jobber doesn’t natively do: that’s the API, which means Plus, which means the $399+/mo gate plus a build.

And one honest subtraction: if what you want is a feature Jobber already ships on your current plan, none of this applies. A surprising number of integration conversations end with us pointing at a Jobber setting.

If you’re staring at that third bucket, integration work is our day job. Our integrations page covers how we build against Jobber, Housecall Pro, ServiceTitan, and CompanyCam, or book a discovery call and bring the workflow that’s bottlenecking you. If a Zap or a marketplace app already solves it, we’ll tell you, and that answer is free.