JobLogic + Salesforce sync for a UK commercial maintenance company
A two-way sync between JobLogic (operational job and asset data) and Salesforce (commercial customer data) for a contractor servicing roughly 600 sites. Eliminates the duplicate-entry problem that had kept the two systems out of step for years.
What was breaking.
Operations lived in JobLogic — work orders, planned maintenance, engineer dispatch, asset history. Sales and account management lived in Salesforce — contracts, renewal dates, opportunities, invoicing. Nobody owned the link between them, so account managers walked into renewals not knowing how many call-outs the customer had had, and ops dispatched engineers to sites where the contract had lapsed.
How I built it.
- Mapped every entity that needed to flow each direction: customer master, sites, contracts, jobs, assets, engineers. Defined system of record per field — contracts owned by Salesforce, jobs owned by JobLogic.
- Built the sync layer in n8n with API connectors on both sides. Handles create, update, soft-delete and conflict resolution per field.
- Implemented idempotency keys so retries and replays don't create duplicates.
- Added a "sync health" dashboard: any record with a divergence between the two systems shows up with the diff so ops or sales can decide which side wins.
- Set up alerts for high-stakes divergences: a job booked against an out-of-contract site triggers a Slack ping to the account manager before the engineer is dispatched.
What makes it tick.
- True two-way sync — not the usual "one system mirrors the other".
- Field-level system of record so neither side can stomp the other's data.
- Audit log of every sync event for compliance — required by the contractor's enterprise customers.
- Bulk back-fill tool used to reconcile years of historical drift in one weekend.
What changed.
Account managers now walk into renewals with a job-history summary auto-pulled from JobLogic. Ops stopped dispatching to lapsed-contract sites — meaningful unbilled work avoided. Renewal close rate improved because conversations shifted from "is everything OK?" to "based on the 47 call-outs you had, here's why a fixed-price contract makes sense".
Tools used.
- JobLogic API
- Salesforce API
- n8n
- PHP
- MySQL
- Slack API
Have a similar workflow problem?
If this looks like the kind of system your business needs, the fastest way to start is a short discovery call.
Book a discovery call