Productivity · Integration
Jobber
Add Jobber to your product for your customers, and give your AI agents governed access to it.
Jobber runs home and field service businesses, and its data model follows the shape of that work: a client at a property raises a request, the request becomes a quote, an approved quote becomes a job, and a job is worked as one or more visits before it is invoiced. An integration that treats a job as a single appointment will get scheduling wrong, because the visit is the thing that lands on a calendar and gets assigned to a crew. The API is GraphQL, which is a real advantage here since a job with its client, property, visits and line items is one query rather than five, but it also means a query cost budget rather than a simple call count. Authorisation is OAuth granted by an admin on each Jobber account, not a key copied from a settings page. Webhooks are signed with an HMAC you verify, have to be answered within a second, and can repeat, so a handler has to be idempotent.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each business authorise its own Jobber account through OAuth, so a job your product creates belongs to the company that will do the work.
Schedule against visits rather than jobs, since a visit is what a crew is actually assigned to on a given day.
Fetch a job with its client, property, visits and line items in one query instead of assembling it from several calls.
Verify the webhook signature and make the handler idempotent, because Jobber resends an event it did not hear back about.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which visits are unassigned this week and which crews have room for them.
An agent creates a quote from an approved request within scoped permissions, with the client it belongs to recorded.
An agent explains why a job has not been invoiced by reading its visits and their completion state.
Example prompt
Which jobs finished last week but have not been invoiced yet, and what is each one worth?
Set up Jobber in 4 steps
- 01Enable the Jobber connector in your fastn dashboard.
- 02Have an admin on each Jobber account authorise your app through OAuth, so calls run under that company's own grant.
- 03Write the GraphQL queries your product needs against jobs, visits and invoices, then register webhooks and verify their HMAC signature.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Jobber integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Jobber integration without building it. Your customers connect their own Jobber account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Jobber update is not your on-call problem.
- One integration serves your product and your agents. The same governed Jobber connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Works well with
Square
QuickBooksOften used alongside
Tools the same teams tend to run next to Jobber, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceJobber integration FAQ
How do I add a Jobber integration to my product?
Enable the Jobber connector in your fastn dashboard, then let each customer authenticate their own Jobber account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Jobber client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Jobber account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Jobber account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Jobber integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which visits are unassigned this week and which crews have room for them.
Who maintains the Jobber integration?
fastn does. When Jobber changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in Jobber automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Jobber can trigger your workflows in return.
Does it adapt to each team's own Jobber setup?
Yes. However a team has configured Jobber, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the Jobber integration?
A common starting point: let each business authorise its own Jobber account through OAuth, so a job your product creates belongs to the company that will do the work. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Jobber integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Jobber does not change your per-connector cost. You can start free with 3 connected accounts.
Add Jobber to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.