Salesforce integration
Salesforce ↔ WordPress
A live two-way pipeline between a complex Salesforce events catalogue and a WordPress front-end.
KWF, via Studio Simpatico, needed their WordPress events catalogue to stay in lockstep with their Salesforce backend. The agency had the WordPress build covered. I built the connectivity layer.
?sfimport, ?sftestmode).salesforce.log. Months of audit trail per API round-trip.Before this, editors mirrored records manually. Two-way drift was constant; trust was low.
After, the team pushed changes on whichever side made sense and the sync did the reconciliation. The admin UI made every sync legible: no silent magic, just a clear diff and a log to come back to.
The hard part of any two-way integration is who owns each piece of data. Get it wrong and you spend the project debugging surprise overwrites.
The rule: editorial control wins. Salesforce owns the shape; if a human touched a record on the WP side, the sync respected that and logged it. Once that hierarchy was clear, every other decision (sync cadence, conflicts, logging, the diff UI) followed.
Done was when the team stopped watching the sync. About six weeks of running in parallel before they skipped the manual step.
The admin UI stayed in use long after launch. Editors kept opening it whenever something complicated was happening, because seeing the diff first was reassuring.
Well-scoped brief, with the usual grey area where Salesforce and WordPress disagree about the world. A couple of short calls a week and a shared edge-case doc kept it moving. This is the kind of work I most enjoy: real editorial users, a non-trivial integration, and an answer that has to remain legible months later.
All case studiesGot an API integration that needs to stay legible months later? That is the kind of work I love.
Misbehaving stack? Codebase that won't play fair?