Ship deep Jobber integrations in days
Jobber exposes clients, quotes, jobs, and invoices through a versioned GraphQL API, and every service business runs its own services, crews, and schedules. With Ampersand, you can get this integration live for your customers in days.
Build a custom data model to handle
complex configurations
No two Jobber accounts are the same. Every customer has their own services, crews, and custom fields, and their own way from request to invoice. AI agents need infrastructure that understands Jobber at the per-tenant level.
3 / 8 customers
- Customer A: Client (standard), Quote (standard), Job (standard)
- Customer B: Request (standard), Visit (standard), Invoice (standard)
- Customer C: Client (standard), Property (standard), Expense (standard)
Enable software and agents to take bi-directional action
With Ampersand, your engineers don’t need to learn Jobber’s GraphQL schema, its API versions, or its webhook topics. Simply declare the actions you want your agents to take: read, write, subscribe, proxy.
Example. Subscribe: “Notify me as soon as a client approves a quote.”
- Ampersand subscribes to quote events through Jobber webhooks it manages.
- Quote approved events arrive, and each carries only the quote’s ID.
- Ampersand fetches the full quote through Jobber’s GraphQL API.
- Ampersand applies this customer’s field mappings.
- Ampersand sends the quote to your product.
Ensure your Jobber integration is always available
-
Managed auth
Fully offload Jobber OAuth. Ampersand stores and refreshes every customer’s tokens for the scopes your Jobber app holds.
-
Managed webhooks
Ampersand creates and manages the Jobber webhook subscriptions when each customer installs your integration, with no setup in the Jobber UI.
-
Lifecycle events
Act the moment a quote is sent or approved, a job closes, or a visit is completed, not only when a record is created, updated, or deleted.
Not all Jobber integrations are created equal
Jobber runs the day-to-day of home service businesses, from the first request to the paid invoice. With Ampersand, your developers can create a best-in-class Jobber integration.
The Jobber objects your agents can read and write
Ampersand reads, writes, and subscribes to Jobber clients, requests, quotes, and jobs, subscribes to visits, invoices, and timesheets, and reads the rest of each account.
Users send created and updated events, but no deleted events. Incremental reads cover capital loans, clients, expenses, invoices, jobs, payout records, quotes, requests, tasks, time sheet entries, and visits; other objects are read in full on each scheduled read.
Questions people ask
before they book a demo
-
Which Jobber objects can I read and write?
You can read and write clients, requests, quotes, jobs, expenses, and vehicles. You can write events, products and services, taxes, and tax groups, and read visits, invoices, properties, users, timesheets, and the rest of each account.
-
Can I get real-time updates from Jobber?
Yes. Subscribe Actions cover 12 objects, including clients, quotes, jobs, visits, and invoices, with created, updated, and deleted events. You can also subscribe to quotes being sent or approved, jobs closing, and visits being completed. Ampersand sets up the webhooks when your customer installs.
-
Does Ampersand read only the records that changed?
For clients, requests, quotes, jobs, visits, invoices, expenses, and a few more, yes: after a full historic backfill, Read Actions pick up only changed records. Other objects are read in full on each scheduled read.
-
Does Ampersand offer a unified API?
Ampersand doesn’t offer a unified API. It works with Jobber’s own objects and fields as each customer sets them up, which differs from how a unified API works. We also give you the primitives to build your own unified data model.