Salesforce with Webflow

Before you wire it

Three things that commonly go wrong.

1. 01

   Validation rules reject writes the website may not surface

   A required field, a picklist value or a rule an admin added later makes the write fail. Without error handling the page may show success even when Salesforce rejects the record, so whether it can say otherwise depends on how the submission path was built.

2. 02

   Web-to-Lead and the API fail differently

   Web-to-Lead works for straightforward lead capture and needs almost no infrastructure. An API write takes more setup and gives more control over validation, error reporting and retries, which is what you want behind a form that feeds your sales process.

3. 03

   Lead and Contact are not the same object

   Which one a submission creates depends on how the org runs its funnel, and getting it wrong means records that are technically present and operationally invisible.

What you are buying

What is included.

• Webflow submissions into Leads, Contacts or the agreed Salesforce object model

• UTM, referrer, campaign and source fields

• Assignment, owner and campaign rules

• Duplicate handling and validation feedback

• Salesforce data back to the site where it is safe and useful