Salesforce is often at the centre of how a business manages its customer relationships, and a well-maintained integration between Salesforce and a website can save significant manual effort. Lead forms that create Salesforce contacts automatically, membership sites that sync user data bidirectionally, event registrations that flow directly into CRM records: these are the kinds of integrations that, when they work properly, become invisible parts of the business. When they break or fall out of date, the cost is felt immediately.
Expression 37 builds and maintains Salesforce integrations for ExpressionEngine and Craft CMS websites. Whether you have an existing integration that needs taking over, a synchronisation that has started failing, or a new connection between your site and Salesforce that needs building, the approach is methodical and the focus is on long-term reliability.
What This Work Covers
- Integration of ExpressionEngine or Craft CMS with Salesforce using the Salesforce REST API
- Bidirectional data synchronisation between website forms and Salesforce objects including Contacts, Leads, Accounts, and Opportunities
- Maintenance of existing Salesforce integrations, including updates following Salesforce API version changes
- Troubleshooting synchronisation failures, authentication issues, and data mapping errors
- Member and user data synchronisation for membership-based websites
- Event registration and form submission workflows that create or update Salesforce records
- OAuth configuration and credential management for secure API access
Common questions:
Our Salesforce integration was built by someone who has left. Can you take it over?
Yes. A code review is the starting point. We assess how the integration authenticates with Salesforce, what data is being sent and received, how errors are handled, and whether the integration is up to date with the current Salesforce API version. From that review we can advise on the current state and provide ongoing maintenance.
Data is not syncing correctly between our website and Salesforce. What is usually the cause?
The most common causes are authentication failures due to expired tokens or changed credentials, changes to the Salesforce object schema that have broken data mapping, API version deprecations, or logic errors in how the integration handles certain edge cases. A proper review of the integration logs and API responses usually identifies the issue quickly.
We want to create Salesforce records automatically from website form submissions. Is that straightforward to implement?
It is a well-understood integration pattern, though the complexity depends on which Salesforce objects need populating, what data mapping is required, and how errors and duplicates should be handled. A clear conversation about your requirements at the outset produces a realistic scope and an integration that actually does what the business needs.
Our Salesforce API version is being deprecated. Do we need to do anything?
Yes. Salesforce retires old API versions periodically, and integrations built against those versions will stop working when they are retired. We assess the impact on your integration, update the API version references, test the updated integration against the new version, and handle any breaking changes in the API response structure.
Can you build a bidirectional sync rather than just sending data to Salesforce?
Yes. Bidirectional synchronisation is more complex because it requires decisions about which system is the source of truth for each data point and how conflicts are handled. It is achievable and we have built bidirectional syncs for membership sites and client portals. The requirements need careful discussion upfront to get the logic right.
