FormAssembly → Salesforce: the mapping mistake that silently drops leads
2 min read
Key takeaway
Leads vanish between FormAssembly and Salesforce when a required Salesforce field — almost
always Company on the Lead — isn't mapped. Salesforce rejects the record, but FormAssembly
still logs the submission as a success, so nothing throws an error and no one notices until the
pipeline looks thin. Validate against the destination, not the sender.
The form submits. The connector logs a success. Marketing swears the campaign is working. And yet the leads aren't in Salesforce. This is one of the most common — and most invisible — integration failures we get called in to fix.
The trap: a required field that isn't mapped
Salesforce Lead requires Company. If your form doesn't collect it and your connector doesn't supply a default, the create call fails validation — but depending on how the connector handles the error, the submission can still be recorded as complete on the FormAssembly side.
Result: a green checkmark on one system, a missing record on the other, and no error anyone will ever see unless they go looking.
Watch out
"Connector succeeded" means the connector ran — not that Salesforce accepted the record. Validate against the destination, not the sender.
Fix it with a field map you actually reviewed
Pull the full mapping and check three things: required destination fields, data-type mismatches, and booleans that need inverting (a "consent" checkbox is often the inverse of HasOptedOutOfEmail).
Tip
Order matters. Run your connector after submission validation, not before — otherwise you map and push data that the form itself would have rejected.
FormAssembly is a genuinely good tool for secure, CRM-connected data collection. The failures are almost never the platform — they're an unreviewed mapping between two systems that each think they did their job. Treat the connection as a governed sync you monitor, not a one-time setup, and these silent drops stop happening.
Related tipInspect a Salesforce Platform Event before you blame middlewareA practical next step
If this looked familiar, check your own Integration Spine.
See where systems, data, ownership and controls may have stopped connecting.
More Bytes
Integration & RevOps7 hard lessons from syncing Salesforce to an ERP
Each of these was paid for in production — including the afternoon a redelivery storm quietly doubled receipts in the general ledger while every dashboard stayed green.
Integration & RevOpsBuy vs. build: when a custom integration actually pays off
Off-the-shelf connectors are the right default. Here's how to tell when your case is the exception that justifies building.
Integration & RevOpsThe real cost of duct-taped MarTech (it isn't the software)
The line item is the subscriptions. The real cost is the senior people spending their week moving data by hand between tools that should talk.