Gemin
Get in touch

Salesforce with Webflow

I connect Webflow forms to Salesforce so submissions reach the right records and the right owners, with accurate attribution, duplicate handling and an alert when something fails.

Start a project

Salesforce integrations like this usually take 3–5 days

What the integration covers

What is included, and what we decide first.

What connects

  • 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

What we figure out first

  • Which forms are worth an API write. Simple lead capture may need less infrastructure, while a form that feeds your sales process is worth the server-side write and the error handling around it. Deciding this per form rather than for the site is what keeps the build proportionate.
  • Credentials need a secure layer. Salesforce API access should not live in Webflow front-end code.
  • Permissions shape the integration. Field-level security, required fields and object access determine what the integration user can actually write.

The risk is not that the form cannot submit. The risk is that it submits, the visitor sees success and Salesforce quietly rejects the record because a required field, duplicate rule or permission setting got in the way.

I map the submission path first and test it with real Salesforce behavior. Then I add the useful parts: ownership, campaign attribution, duplicate handling, queueing for retries and alerts when something breaks.

Web-to-Lead can be the right answer for simple lead capture, especially when speed matters. For forms tied to revenue, I usually prefer a webhook and server-side API write because failures can be logged, reported and fixed instead of guessed at later.

How the handoff works

  1. 01

    Submit

    The form posts from Webflow

  2. 02

    Record

    Created on the agreed object

  3. 03

    Attribution

    Campaign and source on the record

  4. 04

    Routing

    Assignment rules pick an owner

  5. 05

    Verify

    Record created, attribution checked, owner assigned

A thank-you page only confirms what the visitor sees. I check that the lead exists in Salesforce, carries its campaign attribution and reached the right owner. If something fails, the right person is told.

Before you wire it

Common integration pitfalls.

  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.

  4. 04

    Duplicate rules can reject a lead entirely

    An org with strict matching can refuse the write, which is usually correct behavior. I agree up front what should happen to those submissions, so a blocked duplicate becomes a decision rather than a missed follow-up.

Other integrations

Wire up something else?

Reach out and see if we are a good fit.

Start a conversation

Currently booking two to four weeks out.