Website & Development
Connecting Webflow to HubSpot (and your marketing stack): getting leads out of your forms
Copy for AI
Some links in this article are affiliate links. If you choose a tool through one of them, we may earn a commission. It costs you nothing extra and does not change our assessment.
You connect Webflow to HubSpot through one of four routes.
They are the official HubSpot app for Webflow, an embedded HubSpot form, a no-code step with Zapier or Make, or a direct HubSpot API or webhook connection.
The verdict: for a Webflow HubSpot integration, the native app is the fastest start. For reliable field mapping, deduplication and full tracking, an intermediate step is often the better choice.
The native app has been around since 2023 and keeps improving. But it’s still designed for simple lead capture.
Working with a different platform or CRM? The same principles apply. Read the broader approach in connecting your website to your CRM like HubSpot or Salesforce.
Here’s the choice in one picture:
Does Webflow have a native HubSpot connection?
Yes: an official HubSpot app for Webflow links your native Webflow forms directly to HubSpot.
How the app works
According to Webflow’s help center, it’s been available since August 29, 2023.
You connect it once per Workspace before mapping individual forms. The setup runs in three steps:
- Open the app in the Webflow Designer, via the Apps panel.
- Connect your HubSpot account once for the Workspace.
- Map your form fields to HubSpot properties.
The field mapping screen is where most mistakes start:
Submissions are first captured by Webflow and then forwarded to HubSpot, as Webflow’s own guide to the native app explains.
For many sites, that’s enough to receive leads in an orderly way and run basic automation, without code.
Where the app stops
The limitations, however, are real:
- One direction: data mostly runs from Webflow to HubSpot, with no full two-way sync
- No advanced form features: no conditional logic, progressive profiling or smart fields
- Dependency: you rely on how robust the app is at that moment
Rule of thumb: treat the app as a starting point, not automatically as a final solution.
Test thoroughly with real submissions before you rely on it for your lead flow.
When do you choose an embedded HubSpot form?
When you value HubSpot’s built-in functionality more than the visual control in Webflow.
What you gain
You build the form in HubSpot and paste the embed code into a Webflow page.
The big advantage: these features work right away, because the form genuinely belongs to HubSpot:
- tracking
- pre-fill of known contacts
- smart fields
- progressive profiling
What you give up
The downside is design freedom. An embed follows HubSpot’s styling.
That makes it harder to fit seamlessly into your Webflow design than a native Webflow form.
For a sharply styled landing page where every pixel counts toward conversion, that often feels like a compromise.
The in-between option
A custom HTML form that you style entirely in Webflow and that posts to HubSpot.
You get more control over the look, with HubSpot’s tracking underneath. That does require a bit more technical knowledge.
How does a connection via Zapier or Make work?
You place an intermediate step between your Webflow form and HubSpot.
On every new submission, the tool creates or updates the matching record in HubSpot.
Your form stays as it is
You leave your Webflow form exactly as it is, with your own styling, and handle the pass-through outside of it.
This has been the most-used route for years, precisely because you’re free in how you map fields and what happens afterward.
Zapier’s Webflow and HubSpot integration pairs a “New Form Submission” trigger in Webflow with actions such as “Create or Update Contact” in HubSpot.
On HubSpot’s side, Zapier lists 28 triggers and 43 actions, such as “Add Contact to Workflow”.
Here’s Zapier’s own pitch, as one example of the glue layer:
Zapier’s homepage, October 2026. Glue tools like this move data between apps without custom code.
Make works the same way, with a visual scenario builder:
Make’s homepage, October 2026. Same job as Zapier, built as a visual scenario.
The power is in the logic
From a single submission you can, for example:
- clean up fields
- assign a lead to the right owner or list
- send an internal notification
- feed several systems at once
Most marketing automation tools take the same handover.
Our experience: we’ve built flows in HubSpot, ActiveCampaign, Brevo, Make and Zapier. Make and Zapier mostly close the gaps between automations.
Our guide to lead routing shows how to assign leads to the right owner.
What to watch for
Do bear a few things in mind:
- Delay: submissions are polled periodically or pushed through via a trigger
- Cost: at high volumes, the tasks in your subscription add up
- Silent failures: a failed step can quietly lose a lead
So always build in some form of error handling.
When do you move to a direct API or webhook connection?
When reliability, speed and control weigh more heavily than convenience.
How the flow works
Webflow can send a form submission as a form_submission webhook to your own endpoint.
The payload carries the form name, the site ID, the submitted data and a timestamp.
At your endpoint, you validate the data, deduplicate it and write it away via the HubSpot API.
HubSpot’s form submission endpoint accepts the hubspotutk tracking token and consent options alongside the fields.
So you keep activity tracking and permission records intact.
Watch out: HubSpot files that endpoint under its Forms API v3 Legacy docs. Check the current version before you build.
What you get
You then get a decoupled flow with:
- your own retry logic
- an audit trail of exactly what was forwarded
- no intermediary that can change or fail
You manage the logic yourself and know precisely what happens to each submission.
Our experience: our own site runs without Make or Zapier. Everything there is custom built.
Who it’s for
This is the route for teams with serious lead volumes or strict data-quality requirements.
It also fits a setup in which several systems have to stay neatly in sync.
It takes more build and maintenance work, and you need someone to manage the connection.
The trade-off
The more critical and larger your lead flow, the sooner a direct connection’s extra robustness pays for itself.
For an average B2B site with a handful of forms, that’s usually overkill. The app or an intermediate step is enough.
Look at your own situation, and pick the simplest route that brings your leads in reliably.
Once leads land, CRM lead management decides what happens next.
Which Webflow HubSpot route suits you?
It depends on your volume, your technical capacity and how much of HubSpot you want to use.
A simple rule of thumb:
- Few forms, basic lead capture, no developer: start with the official HubSpot app or an embedded form.
- You want to keep your Webflow design and smart routing or clean-up: use Zapier or Make as an intermediate step.
- High volume, strict data quality, multiple systems in sync: go for a direct API or webhook connection.
Here are the four routes side by side:
| Route | Design control | HubSpot features | Reliability | Build effort |
|---|---|---|---|---|
| Official app | Full (native forms) | Basic | Depends on the app | Low |
| Embedded form | Limited | Full | Runs on HubSpot | Low |
| Zapier or Make | Full | Via mapping | Good, with error handling | Medium |
| API or webhook | Full | Via the API | Highest, own retries | High |
What you arrange underneath matters more
More important than the platform debate is what you arrange underneath. Two things decide whether your connection truly delivers value.
1. UTM and source pass-through
Send along the UTM parameters and the page context as hidden fields.
Otherwise leads arrive in HubSpot without an origin. You won’t know which campaign or page produced them.
More on correct origin measurement in our explanation of UTM parameters.
2. Consent
Record that someone agreed and what they ticked.
That way your lead processing complies with the GDPR, and you don’t send unsolicited emails. Our guide to a GDPR-compliant contact form covers the form side.
Don’t forget the form itself
The best connection can’t save a form with too many fields or a weak call to action.
How to build a form people actually fill in, we cover in form conversion optimization.
A good connection ensures every completed lead arrives. Good form UX ensures more are completed.
You need both to turn your site into a working lead machine, as we describe in a B2B website that generates leads.
Where these connections usually break
Our experience: the recurring CRM problems are data out of sync, deals not attributed to the right team and notifications that don’t fire.
Each of them starts at the form-to-CRM handover. So test that handover first.
Frequently asked questions
Do I need a developer for a Webflow HubSpot integration?
Not for the official app, an embedded form or a Zapier or Make step: all three work without code.
A custom HTML form takes some technical knowledge, and a direct API or webhook connection needs someone to build and maintain it.
Does the HubSpot app sync data back to Webflow?
Not in full. The data flow mostly runs from Webflow to HubSpot, so treat it as one-way lead capture rather than a two-way sync.
Can I keep HubSpot tracking with a native Webflow form?
Yes, if you post the submission with the hubspotutk tracking token. HubSpot’s form submission endpoint accepts that token and consent options alongside the fields.
Zapier or Make: which one should I pick?
Both handle the Webflow to HubSpot handover. Pick the one your team already uses, and make sure failed runs trigger an alert.
The short summary
You connect Webflow and HubSpot via the official app, an embedded form, a Zapier or Make step, or a direct API and webhook connection.
The app is the fastest starting point for simple lead capture, but it’s largely one-way and limited in advanced features.
For control, reliability and clean field mapping, an intermediate step or direct connection is often better.
Whatever you choose: set up UTM pass-through and consent, and make sure the form itself converts.
That way every lead comes in with its source and permission, ready for follow-up.
Want us to set up your Webflow site and CRM connection with conversion in mind? Check out our web design service or contact us.
For the bigger picture, start with our guide on building a B2B website.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.