HubSpot
The easiest CRM to connect to Webflow — native forms, tracking, and contact sync.
The HubSpot Webflow integration is the easiest CRM connection you can make on the platform. Instead of routing form submissions through Zapier or Make, HubSpot connects natively: you embed a HubSpot form on a Webflow page (or map an existing Webflow form), enable the HubSpot tracking code site-wide, and submissions create or update contacts inside HubSpot's CRM — lists, workflows, lead scoring, and email sequences included. For marketing teams already standardized on HubSpot, it is the default integration choice, and the only one that needs no automation layer for core lead capture.
What you can do with HubSpot
- Embed HubSpot forms directly on Webflow pages via a Custom Code element — every submission creates or updates a contact with no middleware.
- Track visitors site-wide with the HubSpot tracking code: page views, traffic source, and returning-visitor history are tied to contact records.
- Map native Webflow forms to HubSpot through the "non-HubSpot forms" capture feature, keeping Webflow's styling while syncing to the CRM.
- Trigger automation — welcome emails, lead scoring, list membership, and sales routing fire automatically on form submission.
- Personalize pages with smart content for known contacts, changing calls-to-action or copy based on lifecycle stage or list membership.
- Install in one click from the Webflow Designer, which adds the tracking code automatically with no manual head-code editing.
How the native HubSpot + Webflow integration works
There are three distinct mechanisms, and most sites use more than one.
First, form embedding. You build a form inside HubSpot's form builder (under Marketing > Forms), copy the embed snippet, and paste it into a Webflow Embed element on the page. The form renders inside an iframe, so submissions flow straight into HubSpot contacts, lists, and workflows. You keep HubSpot's progressive profiling, dependent fields, and smart fields — but styling lives in HubSpot's external editor, not the Webflow Designer.
Second, visitor tracking. The HubSpot tracking code, installed once in Site Settings > Custom Code > Head, fires on every page load. It records anonymous traffic source, page views, and returning visits, and the moment a visitor submits a form, that anonymous history gets merged into a known contact record. This is what powers HubSpot's lead intelligence on Webflow sites.
Third, non-HubSpot form capture. If you want to keep a native Webflow form (for full control over styling, layout, or interactions), enable "Capture non-HubSpot forms" in HubSpot's tracking settings. HubSpot then detects Webflow form submissions on the page, extracts the field values, and writes them to a contact — no embed code, no Zapier. The trade-off is that you lose HubSpot-native features like progressive profiling.
What the native integration does not do is write data back to Webflow. HubSpot does not create or update Webflow CMS items, and there is no two-way sync. For reverse flows (deals updating CMS, custom-object triggers), teams layer Zapier or Make on top.
How to connect HubSpot to Webflow
- In HubSpot, go to Settings > Tracking & Analytics > Tracking Code and copy the snippet, or open the HubSpot app from the Webflow Designer for a one-click install.
- In Webflow, open Site Settings > Custom Code and paste the tracking code into Head code. Add your Webflow domain to HubSpot under Additional Site Domains.
- Publish the site so the tracking code goes live — it will not fire on the staging subdomain until published.
- In HubSpot, create a form under Marketing > Forms, configure the fields, then copy the embed code.
- In the Webflow Designer, drag an Embed element onto the page where the form should appear and paste the snippet.
- (Alternative) To keep a native Webflow form, enable Capture non-HubSpot forms in HubSpot tracking settings instead of embedding.
- Submit a test entry, confirm the contact appears in HubSpot, then build a workflow — welcome email, Slack alert, or lead-score bump — on form submission.
HubSpot pricing
The connection is free, but the automation depth depends entirely on your HubSpot tier. The Free CRM is genuinely usable for a small team doing basic lead capture on Webflow; anything beyond simple contact storage and welcome emails pushes you into the paid marketing hubs, where price scales steeply. Marketing Hub Professional is the tier where the integration becomes worth the setup effort, because that is where workflows, lead scoring, and smart content unlock.
| Tier | Price | Key limits | Best for |
|---|---|---|---|
| Free CRM | $0 | Basic forms, contact storage, visitor tracking, limited automation | Solo founders and small teams testing lead capture |
| Starter | ~$9–20 / seat / mo | Email automation, ad retargeting, list segmentation, 2 pipelines | Small marketing teams running simple nurture sequences |
| Professional | ~$800–890 / mo | Workflows, lead scoring, smart content, A/B testing, multi-touch reporting | Growth teams that need real automation from Webflow leads |
| Enterprise | ~$3,600 / mo | Custom objects, partitioning, predictive scoring, advanced permissions | Large orgs running ABM and complex revenue ops |
HubSpot vs. Salesforce for Webflow
For most Webflow sites the choice is straightforward. HubSpot connects natively — install the tracking code, embed a form, and submissions land in the CRM with no third-party automation. Salesforce has no native Webflow connector; every flow runs through Zapier or Make, which adds subscription cost, latency, and a failure point that breaks silently when a field schema changes. Salesforce becomes the right pick only when it is already the system of record and the organization mandates it; everyone else gets more value, faster, from HubSpot.
| Dimension | HubSpot + Webflow | Salesforce + Webflow |
|---|---|---|
| Connection | Native (tracking code + forms) | Middleware only (Zapier or Make) |
| Setup time | Minutes to an hour | Hours, plus Zapier/Make config |
| Cost to start | $0 (Free CRM) | Salesforce seat + Zapier subscription |
| Failure surface | Single native path | Two platforms (middleware + CRM) |
| Best fit | Marketing-led growth teams | Enterprise sales orgs already on Salesforce |
Best HubSpot + Webflow use cases
Lead capture into segmented nurture
Demo, quote, and contact submissions flow into HubSpot contacts and auto-enroll into segmented lists and email sequences based on form or page. No manual routing, no nightly exports.
Visitor tracking and lead intelligence
The tracking code records every page view and traffic source, so when an anonymous visitor finally submits a form, their full browsing history attaches to the contact record. Sales sees what they read before reaching out.
Smart content personalization
Once a visitor is a known contact, HubSpot smart content swaps headlines, calls-to-action, or page sections based on list membership or lifecycle stage — turning a static marketing site into a personalized experience.
Event and webinar registration
Multi-field registration forms with progressive profiling collect the right data on each visit, auto-confirm via email, and trigger reminder sequences — built and managed in HubSpot, surfaced on Webflow.
Hand-raiser routing to sales
High-intent submissions (pricing page, enterprise demo) trigger workflows that assign a contact owner, post a Slack alert, and create a task — turning the Webflow form into the front door of your sales process.
Limitations to know
- Embedded forms are styled in HubSpot, not Webflow. They render in an iframe and bypass the Webflow Designer's typography and layout system, which can frustrate design teams chasing pixel parity.
- Advanced automation needs a paid tier. Workflows, lead scoring, and smart content require Marketing Hub Professional (~$800+/mo), so the free integration only takes you so far.
- No two-way CMS sync. HubSpot cannot create or update Webflow CMS items; reverse flows require Zapier or Make layered on top.
- Pricing scales steeply. The gap between Starter and Professional is roughly 40x per month, which catches growing teams off guard when they outgrow the free tier.
Related Webflow integrations
- Salesforce — the enterprise alternative, always via middleware.
- Zapier — extends HubSpot with custom objects, deal updates, and reverse flows into Webflow CMS.
- Mailchimp — the lighter-weight pick for teams that need email marketing but not a full CRM.
- Intercom — conversational lead capture and support alongside HubSpot forms.
- Blog: 20 Best Webflow Integrations to Use in 2026.
Frequently asked questions
Yes. Webflow has a native HubSpot integration available from the Webflow Designer and the HubSpot marketplace. You install the HubSpot tracking code (or use the one-click app), then either embed a HubSpot form on a page via a Custom Code element or map an existing native Webflow form through the non-HubSpot forms feature. Submissions create or update HubSpot contacts automatically, with no Zapier or Make required for the core flow.
The connection itself is free, and HubSpot's Free CRM tier covers basic form embedding, contact storage, and visitor tracking for a small team. The free tier has limited automation, list segmentation, and reporting. To trigger workflows, lead scoring, sequences, and smart content you need a paid tier — Marketing Hub Professional starts around $800 to $890 per month, so the integration is free but the automation capabilities that justify it are not.
HubSpot is better for most Webflow sites because it connects natively — no middleware, lower cost to start, and a learning curve suited to marketing teams. Salesforce is the better fit for large enterprises that already run on it, but it has no native Webflow connector and always requires Zapier or Make, which adds cost, latency, and a failure point. Pick HubSpot unless Salesforce is mandated by your organization.
Install the HubSpot tracking code in Webflow under Site Settings > Custom Code > Head code (or via the one-click HubSpot app), then publish. In HubSpot, create a form under Marketing > Forms and copy its embed code. In the Webflow Designer, drag an Embed element onto the page and paste the snippet. Alternatively, enable non-HubSpot form capture in HubSpot settings to map an existing native Webflow form without embedding. Test with a real submission to confirm the contact appears in HubSpot.
Yes. The HubSpot tracking code installed in your Webflow site head records page views, traffic sources, and returning visitors for every page where it loads. For known contacts (anyone who has submitted a form), HubSpot ties browsing history to the contact record and feeds it into lists, lead scoring, and smart content. Anonymous visitor tracking is included on every plan, including Free.
Launch faster with Webflow templates
Every template is CMS-ready and integration-friendly — connect your tools and ship.









