Salesforce integration

Kurt Weill Foundation

Salesforce ↔ WordPress

A live two-way pipeline between a complex Salesforce events catalogue and a WordPress front-end.

What I did

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.

  • WordPress integration against the official PHP Salesforce SDK, upserting Event__c records and their relations into two custom post types.
  • Two-minute background WP-cron sync, plus on-demand triggers (?sfimport, ?sftestmode).
  • Duplicate cleanup on the Salesforce side before records reach the live site.
  • An ACF admin UI showing editors exactly what is about to change before the sync runs.
  • A persistent salesforce.log. Months of audit trail per API round-trip.

How it helped

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.

Why this way

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.

What "done" looked like

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.

Working together

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 studies
Hire me

Let's talk.

Got an API integration that needs to stay legible months later? That is the kind of work I love.