Spectrum

Clouver built a secure API layer that sits between the two platforms. It was delivered in phases over about five months: token management first, then the proxy, then the Salesforce sync, then the bulk matching.

• Authenticated GraphQL proxy: a single endpoint that accepts Jobber queries and mutations, handles OAuth automatically, and preprocesses variables into Jobber’s schema (ID encoding, custom field mapping, scheduling format conversion)

• Automatic Salesforce records: when a job is created through the proxy, a linked Jobber record is created in Salesforce against the matching opportunity, closing the loop between sales and operations

• Self-refreshing OAuth tokens: access tokens are cached in Redis and refreshed every 30 minutes by a scheduled job, so nobody re-authenticates by hand

• Technician auto-assignment: the system reads the email in the job notes, looks it up in Jobber’s user directory, and assigns the matching person to the job

• Bulk property matching: every Jobber property is compared against every Salesforce account using normalized addresses, edit distance, and token similarity, then scored as strong (address and client name match) or weak (address only)

• Account backfill: matched Salesforce accounts are updated in batches with their Jobber property IDs, enabling cross-system lookups going forward

Before:

• Job details re-typed from Salesforce into Jobber

• No way to tell from Salesforce whether a sold job was scheduled

• OAuth tokens expired silently and broke integrations

• Thousands of properties with no link to their account

• Technician assignment required a manual lookup

After:

• Jobs created in Jobber with a single API call, with the Salesforce record linked automatically

• Every job tied to its opportunity, visible from Salesforce

• Tokens refresh every 30 minutes with zero manual intervention

• Existing properties matched to accounts with confidence scores

• Technicians assigned automatically from the job notes