Salesforce

The Salesforce Webflow integration turns Webflow form submissions and ecommerce orders into Salesforce Leads, Contacts, and custom records. The single most important thing to know up front: there is no native connector. Unlike HubSpot, Salesforce never touches Webflow directly — every connection runs through an automation layer like Zapier or Make. For enterprise teams where Salesforce is already the system of record, that middleware-based link is reliable, well documented, and the standard way to connect the two. For smaller sites or marketing-led teams, it is usually overkill compared to a native CRM.

What you can do

• Webflow form to Salesforce Lead or Contact — turn a New Form Submission into a Lead or Contact in real time.
• Create, update, find, and find-or-create records to deduplicate instead of stacking duplicates on every submission.
• Sync ecommerce orders — map Webflow New Order and Updated Order events to custom order or transaction records.
• Write to any object — Leads, Contacts, Accounts, Cases, Opportunities, and Custom Objects via the generic Create Record action.
• Run multi-step automation — enrich inbound data, branch with filters, or fan one submission out to several Salesforce objects in a single Zap.
• Trigger actions from Salesforce — new or updated Salesforce records can drive actions back in Webflow or other tools, so the bridge is bidirectional.

How Webflow connects to Salesforce

Because there is no native Salesforce Webflow integration, the two platforms meet in the middle through middleware. The model is always the same: one app provides a trigger and Salesforce receives the action.

On the Webflow side, the supported triggers are New Form Submission, New Order, Updated Order, New Comment, and New/Updated CMS Item. Zapier and Make both use instant webhook triggers for Webflow forms, so submission-to-record latency is usually a few seconds. On the Salesforce side, the common actions are Create Lead, Create Contact, Create Record (for any object), Update Record, Find or Create Record for deduplication, Add to Campaign, Convert Lead, and Send Email. Supported objects span Leads, Contacts, Accounts, Cases, Opportunities, and Custom Objects across Sales Cloud and Service Cloud, and Zapier also exposes advanced actions like running SOQL/SOSL queries, launching a Flow, or calling custom Apex. Webflow never talks to Salesforce directly, which is why the choice and configuration of your middleware tool is the part that actually defines the integration.

How to connect Webflow to Salesforce

1. Create a Zapier account at zapier.com and click Create a Zap.
2. Set the trigger to Webflow → New Form Submission, authenticate your Webflow account, and select the site and the specific form.
3. Set the action to Salesforce → Create Lead (or *Create Contact*, *Create Record*, or *Find or Create Record*).
4. Authenticate your Salesforce account inside Zapier using OAuth.
5. Map fields from Webflow to Salesforce — for example, Webflow "Name" → Salesforce "LastName", Webflow "Email" → "Email".
6. Enable Find or Create for deduplication so repeat submissions update existing records instead of creating duplicates.
7. Test with a real form submission, confirm the record appears in Salesforce, then turn the Zap on.

For complex objects (Opportunities, Custom Objects, Cases), use the generic Create Record action and specify the object type. Make follows the same pattern with a visual scenario builder, and tends to be cheaper at higher volume.

Salesforce + Webflow pricing

There is no bundled Webflow-Salesforce pricing. You pay for the CRM seats and, separately, for the middleware that bridges the two. Salesforce is the dominant cost by far; the automation tool is comparatively minor but metered on volume.

Salesforce vs. HubSpot for Webflow

For most Webflow sites the real decision is Salesforce versus HubSpot, and they sit at opposite ends. HubSpot is built for fast, native lead capture from Webflow; Salesforce is the heavy enterprise system you pick when it is already mandated.

Best use cases

Enterprise lead capture

Route high-value Webflow demo, quote, and contact forms straight into Salesforce Leads with lead assignment rules and campaign attribution intact.

Lead-to-opportunity conversion

Push qualified Webflow leads through enrichment, then convert them to Contacts and Opportunities inside your existing Salesforce pipeline.

E-commerce order sync

Map Webflow New Order and Updated Order events to custom order or transaction records so finance and sales see the same data.

Support case creation

Turn Webflow support or request forms into Cases in Service Cloud, complete with priority, subject, and contact linkage.

Account-based enrichment

Enrich inbound Webflow leads with firmographic data in a multi-step Zap before the Salesforce record is created, so reps work from clean data.

Limitations to know

• Not native. You always pay for and depend on Zapier or Make, which adds latency and a failure point between Webflow and Salesforce.
• File attachments are capped at 25 MB. Zapier's Salesforce Create Attachment and Create File actions enforce a strict 25 MB maximum, and Webflow file-upload fields often need a Webhook or external storage (S3, Cloudinary) workaround before reaching Salesforce.
• No Salesforce Marketing Cloud connector. SFMC is not available on Zapier — that path needs custom API work or a different middleware platform.
• Field mapping is brittle. Rename or restructure a field in either platform and the mapping can break silently; retest after any schema change.

Related Webflow integrations

• HubSpot — the native Webflow CRM alternative, no middleware required.
• Zapier — the most common middleware for the Salesforce connection.
• Make — the visual, lower-cost alternative for complex Salesforce routing.
• Blog: 20 Best Webflow Integrations to Use in 2026.