What This Integration Does
This integration pushes lead data from your WordPress site directly into Salesforce, creating Lead or Contact records with the correct owner assignment, record type, and field values — all through Salesforce’s REST API, not through web-to-lead forms or third-party connectors.
Salesforce’s native web-to-lead feature is limited. It does not support conditional field mapping, record type selection, or owner assignment based on form data. It cannot check for existing records before creating new ones. This integration replaces that with a proper API connection that treats every form submission as structured data to be routed into the right place in your Salesforce org.
When a form is submitted on your WordPress site, the integration determines whether the person already exists in Salesforce, decides whether to create a Lead or update an existing Contact, maps every field to the correct Salesforce field (including custom fields), and assigns the record to the right user or queue based on rules you define.
The Workflow
A form submission fires a server-side event in WordPress. The integration takes the submission data and authenticates against Salesforce using the OAuth 2.0 JWT bearer flow — no stored passwords, no session tokens expiring mid-sync.
Before creating a record, the integration queries Salesforce’s SOQL API to check whether a Lead or Contact with that email address already exists. If a match is found, the existing record is updated with any new information. If no match is found, a new Lead is created with the record type, lead source, and owner assignment determined by the form type and field values.
For sites with territory-based routing, the integration reads Salesforce assignment rules and applies them during record creation. Campaign membership is set if the form corresponds to a tracked marketing campaign. The entire process happens in a background queue so the visitor sees their confirmation page without delay.
Before and After
Before: Web-to-lead forms dump every submission into Salesforce as an unassigned Lead with minimal data. Someone in operations manually reassigns leads, fills in missing fields, and checks for duplicates. High-value leads from specific service pages receive the same treatment as generic contact form submissions. Campaign attribution is inconsistent or absent.
After: Every form submission arrives in Salesforce with complete field mapping, correct record type, and immediate owner assignment. Leads from different form types are routed to different queues or users automatically. Existing contacts are updated rather than duplicated. Campaign membership is set at the point of creation, giving marketing accurate attribution data from day one.
Who Needs This
This integration suits organisations that run their public-facing site on WordPress and manage their sales pipeline in Salesforce. It is the right fit if:
- You have outgrown Salesforce’s web-to-lead forms and need conditional logic, duplicate checking, or owner assignment at the point of capture
- Your Salesforce org uses multiple record types, and different form types should create different record types
- You need campaign membership set automatically when leads come through specific landing pages or forms
- Your sales team complains about incomplete records, unassigned leads, or duplicates in their pipeline
- You have custom fields in Salesforce that are critical for lead qualification and cannot be captured through native web-to-lead
How We Build This
We begin with your Salesforce data model — which objects, record types, fields, and assignment rules are in play. We map every WordPress form field to its Salesforce counterpart, identify custom fields that need to be created or adjusted, and document the routing logic for each form type.
The integration authenticates via Salesforce’s OAuth 2.0 JWT bearer flow, which is designed for server-to-server communication and does not require a logged-in user session. Record creation and updates go through Salesforce’s REST API with composite requests where multiple related objects need to be created in a single transaction.
Duplicate detection uses SOQL queries against email address, with configurable fallback matching on name and company. Rate limiting and retry logic ensure the integration respects Salesforce’s API call limits, which are finite per 24-hour period depending on your Salesforce edition. Every API call is logged with request and response data for debugging.
We test against your Salesforce sandbox first, verifying record creation, field mapping, duplicate handling, and assignment rules across every form type. Once validated, we deploy against production with monitoring in place.
Start Routing Leads Into Salesforce Automatically
If your WordPress leads are arriving in Salesforce incomplete, unassigned, or duplicated, the problem is not your sales team — it is the connection between your website and your CRM. We build the integration that fixes it.
Get in touch to discuss your WordPress and Salesforce integration.
Related pages:
Alex
I’m a software developer and CEO of Digital Royalty, helping growing teams scale their SaaS platforms without losing quality, visibility, or control. I focus on building structured, maintainable systems with clear processes, reporting, and accountability. With over a decade of experience across agency and in-house roles, I specialise in delivering long-term, scalable solutions that support complex, evolving products.