Jobber
Integrations › Jobber
Field Service

Jobber Integration

Turn ad leads into Jobber clients and service requests automatically -- so your field service team gets new jobs in their schedule without manual data entry.

Available Integrations

Connect Jobber with 4 lead sources

Start Free Trial No credit card required · 14-day free trial
Trusted by
1,000+ businesses
Leads synced
2M+
Integrations
37+
Free trial
14 days, no card

How It Works

1
Connect Your Ad Account
Link your Facebook, Google, LinkedIn, or TikTok ad account to LeadSync in one click.
2
Choose Jobber
Select Jobber as your destination and authenticate your account.
3
Map Your Fields
Match your lead form fields to Jobber and start syncing leads instantly.

How Facebook Leads Become Jobber Clients

When a Facebook lead form is submitted, LeadSync creates a new Client in your Jobber account using Jobber's GraphQL API -- with the lead's name, email, phone number, and street address mapped to the matching client fields. If your lead form captures additional information (project type, square footage, preferred service window), LeadSync attaches a Note to the new Client containing those details so the work order context is preserved when your team picks up the job.

Setup is OAuth -- click Jobber in the LeadSync destination list, authorise the connection in your Jobber account, and you're running. No API keys to manage, no IT setup required at the business level, no middleware sitting between Jobber and your ad accounts.

GraphQL, Token Refresh, and the Reconnect Email

Jobber's API is GraphQL rather than REST, which means LeadSync sends a single mutation per lead containing exactly the fields Jobber expects -- no round-tripping through generic REST endpoints, no extra calls to fetch related objects. Token refresh happens automatically: Jobber access tokens expire after 60 minutes, but the refresh token (rotated on every refresh, per Jobber's OAuth spec) is stored and used the moment the access token fails.

If the refresh token itself ever becomes permanently invalid -- which can happen if you remove LeadSync's app from Jobber, or if Jobber's OAuth server times out the long-lived token after extended inactivity -- LeadSync detects this on the very next lead, marks the connection as needing reconnection, and sends you a one-time email with a direct link back to the LeadSync connections page. No silent failures, no leads lost in the gap between disconnect and your next manual check.

Multi-Business and Multi-Page Routing

Field service operators often run multiple Jobber accounts -- one per business unit, one per franchise location, one per service brand. LeadSync handles this with separate connections per Jobber account: each connection has its own OAuth credentials, its own field mapping, and its own destination behaviour. Route Facebook leads from your "Plumbing" page to one Jobber account, route leads from your "HVAC" page to a different account, and they never cross-contaminate.

On the Facebook side, this also lets you route from multiple Pages: each Page can drive a different LeadSync connection pointing at a different Jobber instance. If you're running ads for a franchise group or multi-location operator, this is the structure that keeps each location's pipeline clean.

Frequently Asked Questions

Click Jobber in the LeadSync destination list and authorise the OAuth connection from your Jobber account. LeadSync uses Jobber's standard OAuth flow, so no API keys are required. The whole setup takes about 30 seconds.
A new Client record with the lead's name, email, phone, and street address (if captured on the form). If your lead form has additional questions, those are attached to the Client as a Note so your team has the full context when they pick up the job.
Jobber's public API is GraphQL-only, so LeadSync sends a single mutation per lead containing exactly the fields Jobber expects. This is more efficient than the typical multi-call REST pattern and avoids issues with Jobber rate-limiting individual REST endpoints.
Jobber access tokens last 60 minutes -- LeadSync refreshes them automatically using the stored refresh token whenever an API call fails. The rotated refresh token is persisted back to your connection record so the next refresh works correctly. You never need to reconnect unless the refresh token itself becomes invalid.
If Jobber's OAuth server permanently invalidates your refresh token (usually because the LeadSync app was removed from Jobber, or extended inactivity timed it out), LeadSync detects this on the next lead, marks the connection as needing reconnection, and sends you a one-time email with a direct link to reconnect. No silent failures.
Yes. Create one LeadSync connection per Jobber account -- each has its own OAuth authorisation, field mapping, and destination behaviour. This is the right structure for franchise groups, multi-brand operators, or businesses with separate Jobber instances per service line.
Yes. Each LeadSync connection points one or more Facebook lead forms at one Jobber account. Run multiple connections in parallel and you can route your Plumbing Page leads to one Jobber instance and your HVAC Page leads to a different one without any cross-contamination.
Yes. LeadSync supports Jobber as a destination for lead forms from Facebook, Instagram, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each ad source becomes its own connection.

Start Syncing Leads to Jobber

Set up your Jobber integration in under 60 seconds. Free 14-day trial, no credit card required.

Start Your Free Trial
No credit card required • Set up in 60 seconds • Cancel anytime