How to Integrate HubSpot Forms Into Webflow: The Best Methods in 2026

Written by
William Lee
October 14, 2026
6 min read
Want to use HubSpot forms on your Webflow site? This guide covers the best integration methods — from native embeds to Zapier automation — so your leads flow directly into your CRM without any friction.

Introduction

If your business runs on HubSpot and your website is built on Webflow, connecting the two is not optional. It is essential.

The good news is that there are multiple ways to do it, and the right method depends on how much design control you need and how complex your lead flows are. This guide covers every approach clearly so you can pick the one that fits your setup.

We have implemented HubSpot integrations for several of our Webflow clients, so everything here comes from real project experience.

Method 1: HubSpot Form Embed

This is the simplest option. You take HubSpot's native embed code and paste it into a Webflow Embed element. The form renders on your site and submissions go directly into HubSpot.

How to set it up:

  1. In HubSpot, go to Marketing, then Lead Capture, then Forms
  2. Create or select your form and click Share
  3. Copy the embed code snippet
  4. In Webflow Designer, add an Embed element where you want the form to appear
  5. Paste the HubSpot embed code into the element
  6. Publish your Webflow site

What works well:

  • Fastest to set up, typically under 10 minutes
  • All HubSpot form logic works natively, including conditional fields and progressive profiling
  • Submissions go directly into HubSpot with full contact property mapping

What to watch out for:

  • Form styling is controlled by HubSpot, not Webflow
  • Custom CSS overrides are needed to match your site design
  • The HubSpot script adds some page weight

Method 2: Webflow Native Form with HubSpot Integration

This is the recommended approach for most SaaS websites and design-critical projects. You build your form entirely in Webflow for full visual control, then connect it to HubSpot via Zapier, Make, or the HubSpot API.

How to set it up:

  1. Build your form using Webflow's native Form element
  2. Name each field to match your HubSpot contact properties, for example email, firstname, company
  3. Connect via Zapier by setting a trigger for New Form Submission in Webflow and an action to Create or Update Contact in HubSpot
  4. Map your form fields to the correct HubSpot properties in Zapier
  5. Test with a live submission before going live

What works well:

  • Full design control, your form matches your site perfectly
  • No HubSpot script weight on the page
  • More flexibility for complex workflows like triggering sequences, tagging contacts, or notifying your team in Slack

What to watch out for:

  • Requires a Zapier or Make subscription, or custom development time
  • Progressive profiling does not work natively without additional logic
  • More initial setup compared to the embed method

Which Method Should You Choose

Here is a simple decision guide:

  • Simple contact form with basic styling needs - Use the HubSpot embed method
  • Design-critical forms on key pages like your homepage or pricing page - Use Webflow native form plus Zapier or Make
  • Complex workflows with multiple sequences and conditional logic - Use Webflow native form plus Make plus the HubSpot API directly

For most startup websites, we recommend Method 2. The design quality difference on high-converting pages is significant, and the Zapier setup takes less than an hour once you know what you are doing.

Troubleshooting Common Issues

A few things that trip people up when connecting Webflow and HubSpot.

HubSpot form not submitting? Check that your Webflow site is published to a live domain, not just previewed. HubSpot forms require the published domain to work correctly.

Zapier not picking up new submissions? Verify that the Webflow form Name attribute matches exactly what Zapier expects. Always test by submitting a real form entry after setting up the Zap, not using Zapier's sample data.

Styling issues with the HubSpot embed? Use the HubSpot form editor's built-in style override settings first. For deeper customization, add CSS to your Webflow page's custom code targeting HubSpot's class structure.

Connecting HubSpot Tracking to Webflow

Beyond forms, you should also install the HubSpot tracking code site-wide on your Webflow site. This enables HubSpot analytics, live chat, and contact activity tracking across all pages.

To do this, go to Site Settings in Webflow, then Custom Code, then paste your HubSpot tracking script into the Head Code section. Once published, HubSpot will start logging page views and session data for every visitor.

This is something we set up as standard practice on all of our Webflow builds for clients using HubSpot.

Conclusion

For most business sites, the Webflow native form plus Zapier or Make integration gives the best balance of design quality and data reliability.

The HubSpot embed is a solid fallback when you need something up quickly and styling is not a priority. But for any page where conversion rate matters, building the form natively in Webflow and piping data to HubSpot through an automation tool is the better long-term setup.

If you want help with your Webflow setup or HubSpot integration, explore our Webflow development services or reach out to discuss your project.

How to Integrate HubSpot Forms Into Webflow: The Best Methods in 2026

Written by
William Lee
October 14, 2026
6 min read
Want to use HubSpot forms on your Webflow site? This guide covers the best integration methods — from native embeds to Zapier automation — so your leads flow directly into your CRM without any friction.

Introduction

If your business runs on HubSpot and your website is built on Webflow, connecting the two is not optional. It is essential.

The good news is that there are multiple ways to do it, and the right method depends on how much design control you need and how complex your lead flows are. This guide covers every approach clearly so you can pick the one that fits your setup.

We have implemented HubSpot integrations for several of our Webflow clients, so everything here comes from real project experience.

Method 1: HubSpot Form Embed

This is the simplest option. You take HubSpot's native embed code and paste it into a Webflow Embed element. The form renders on your site and submissions go directly into HubSpot.

How to set it up:

  1. In HubSpot, go to Marketing, then Lead Capture, then Forms
  2. Create or select your form and click Share
  3. Copy the embed code snippet
  4. In Webflow Designer, add an Embed element where you want the form to appear
  5. Paste the HubSpot embed code into the element
  6. Publish your Webflow site

What works well:

  • Fastest to set up, typically under 10 minutes
  • All HubSpot form logic works natively, including conditional fields and progressive profiling
  • Submissions go directly into HubSpot with full contact property mapping

What to watch out for:

  • Form styling is controlled by HubSpot, not Webflow
  • Custom CSS overrides are needed to match your site design
  • The HubSpot script adds some page weight

Method 2: Webflow Native Form with HubSpot Integration

This is the recommended approach for most SaaS websites and design-critical projects. You build your form entirely in Webflow for full visual control, then connect it to HubSpot via Zapier, Make, or the HubSpot API.

How to set it up:

  1. Build your form using Webflow's native Form element
  2. Name each field to match your HubSpot contact properties, for example email, firstname, company
  3. Connect via Zapier by setting a trigger for New Form Submission in Webflow and an action to Create or Update Contact in HubSpot
  4. Map your form fields to the correct HubSpot properties in Zapier
  5. Test with a live submission before going live

What works well:

  • Full design control, your form matches your site perfectly
  • No HubSpot script weight on the page
  • More flexibility for complex workflows like triggering sequences, tagging contacts, or notifying your team in Slack

What to watch out for:

  • Requires a Zapier or Make subscription, or custom development time
  • Progressive profiling does not work natively without additional logic
  • More initial setup compared to the embed method

Which Method Should You Choose

Here is a simple decision guide:

  • Simple contact form with basic styling needs - Use the HubSpot embed method
  • Design-critical forms on key pages like your homepage or pricing page - Use Webflow native form plus Zapier or Make
  • Complex workflows with multiple sequences and conditional logic - Use Webflow native form plus Make plus the HubSpot API directly

For most startup websites, we recommend Method 2. The design quality difference on high-converting pages is significant, and the Zapier setup takes less than an hour once you know what you are doing.

Troubleshooting Common Issues

A few things that trip people up when connecting Webflow and HubSpot.

HubSpot form not submitting? Check that your Webflow site is published to a live domain, not just previewed. HubSpot forms require the published domain to work correctly.

Zapier not picking up new submissions? Verify that the Webflow form Name attribute matches exactly what Zapier expects. Always test by submitting a real form entry after setting up the Zap, not using Zapier's sample data.

Styling issues with the HubSpot embed? Use the HubSpot form editor's built-in style override settings first. For deeper customization, add CSS to your Webflow page's custom code targeting HubSpot's class structure.

Connecting HubSpot Tracking to Webflow

Beyond forms, you should also install the HubSpot tracking code site-wide on your Webflow site. This enables HubSpot analytics, live chat, and contact activity tracking across all pages.

To do this, go to Site Settings in Webflow, then Custom Code, then paste your HubSpot tracking script into the Head Code section. Once published, HubSpot will start logging page views and session data for every visitor.

This is something we set up as standard practice on all of our Webflow builds for clients using HubSpot.

Conclusion

For most business sites, the Webflow native form plus Zapier or Make integration gives the best balance of design quality and data reliability.

The HubSpot embed is a solid fallback when you need something up quickly and styling is not a priority. But for any page where conversion rate matters, building the form natively in Webflow and piping data to HubSpot through an automation tool is the better long-term setup.

If you want help with your Webflow setup or HubSpot integration, explore our Webflow development services or reach out to discuss your project.

Frequently Asked Questions

Can I use HubSpot forms on a Webflow site?

Does embedding a HubSpot form break Webflow's design?

Will HubSpot track analytics from Webflow form submissions?

Is Zapier required to connect Webflow to HubSpot?

What is the easiest way to add HubSpot to Webflow?

How do I connect Webflow forms to HubSpot without coding?

Can I style a HubSpot form to match my Webflow site?

What is the HubSpot Forms API and do I need it for Webflow?

Ready to build something coherent?

Let's talk. We're dedicated to bringing your vision to life.

sample glossary link
search-intent
Search intent
The reason behind a search - learning, comparing, or buying. "What is AEO" and "AEO agency near me" are different intents and need different content.
featured-snippet-people-also-ask
Featured snippet / People Also Ask
Google's answer boxes that appear above or inside the link list. Like FAQ blocks, they're easy pickings for AI answer engines.
robots-txt
robots.txt
A file that tells crawlers what to read and what to skip. It's how you keep draft or private pages out of search results.
sitemap
Sitemap (sitemap.xml)
A file listing every page on your site, submitted so crawlers can find them all.
core-web-vitals
Core Web Vitals
Google's speed and usability scores for your pages. Slow, awkward pages get buried in both search and AI citations.
ga4
GA4 (Google Analytics 4)
Google's free dashboard showing who visits your site and where they come from - including AI-referred visitors. The default way to measure whether all of this is working.
ai-referred-traffic
AI-referred traffic
Visits to your website that started with an AI answer. You can see this in analytics as a traffic source, alongside Google and social.
sentiment
Sentiment
Whether the AI describes your brand positively, neutrally, or negatively. AI usually reflects what your site and third-party pages say, so sentiment is fixable.
mention-rate
Mention rate
How often your brand is mentioned at all in AI answers, with or without a link. Mentions matter because they shape what customers remember.
citation-rate
Citation rate
The percentage of AI answers about your industry that cite your website as a source. Most companies today are cited in well under 10% of answers - the bar is low and the opportunity is real.
share-of-voice
Share of voice
How often AI answers mention your brand compared to competitors. This replaces "keyword ranking" as the scoreboard in an AI-search world.
faq-content
FAQ content
Question-and-answer blocks on your pages. Both Google and AI tools lift answers straight from these, which makes them one of the easiest AEO wins.
authority-e-e-a-t
Authority / E-E-A-T
How trustworthy search engines and AI judge your site: Experience, Expertise, Authoritativeness, and Trust. Show who writes your content and why they know the topic.
indexing
Indexing
Being stored in a search engine's or AI system's database so you can appear in results. A crawled page that isn't indexed is invisible.
crawling
Crawling
The process of search and AI bots reading your website. If bots can't read your pages, you can't rank or be cited.
llms-txt
llms.txt
A small file on your website that tells AI tools which pages to read. Think of it as a table of contents written for robots.
entity
Entity
The machine-readable version of who your business is: consistent name, logo, contact details, and social profiles across the web. AI tools stitch these together to decide what to say about you.
schema-markup
Structured data / schema markup
Extra code on your pages that spells out what your content is - your business name and address, FAQs, reviews, articles - in a format machines can read. It is the difference between "a webpage" and "a business record."
rag
RAG (Retrieval-Augmented Generation)
How answer engines work: they first pull real content from the web, then generate an answer from it. This is why your website copy feeds AI answers - and why AEO works at all.
hallucination
Hallucination
When AI confidently says something false. For a business, this matters: an AI may describe your services, pricing, or hours incorrectly, and customers will believe it unless your website tells the correct story.
ai-citation
AI citation / AI mention
When an answer engine names your business or links your site as a source. Being cited builds trust; being left out means AI customers never hear about you.
geo
GEO (Generative Engine Optimization)
The same practice as AEO under a different name. Treat them as one thing.
aeo
AEO (Answer Engine Optimization)
Getting your business cited and recommended when customers ask AI tools about your industry. If SEO is ranking in a list, AEO is being the named source in the answer.
ai-overview
AI Overview (AIO)
Google's AI answer box at the top of some search results. It summarizes sources - including possibly your website - before the regular link list.
generative-ai
Generative AI (gen AI)
AI that creates new text, images, or code rather than just finding existing content. ChatGPT is the most famous example.
llm
LLM (Large Language Model)
The AI technology behind answer engines. It predicts text based on patterns learned from huge amounts of writing. When people say "the AI," they usually mean an LLM.
answer-engine
Answer engine
A tool that answers your question directly with a written, cited answer instead of a list of links. The main ones: ChatGPT, Gemini, Perplexity, and Google's AI Overviews.
zero-click-search
Zero-click search
A search that ends without any click because the answer is shown right on the results page - a snippet, a map, or an AI answer. More than half of searches now end this way, which is the whole reason AEO exists.
click-through-rate
Click-through rate (CTR)
The share of people who see your business in results and actually click. Low CTR usually means your listing doesn't match what people searched for.
keyword
Keyword
The word or phrase a customer types, like "Webflow agency Toronto" or "SEO audit for my website." Most search and AI strategies start with knowing which keywords your customers use.
seo
SEO (Search Engine Optimization)
Improving your website so it ranks higher in search results. Historically this meant keywords, titles, and links; today it also includes feeding AI tools.
map-box
Map box (map pack)
The map Google shows for location-based searches like "dentist near me" or "webflow agency toronto," usually with three businesses listed next to it. For local searches, the map box gets most of the attention and clicks, so being in it can matter more than ranking first in the regular links.
answer-box-featured-snippet
Answer box (featured snippet)
The box at the top of some Google results that answers the question directly with a short paragraph, list, table, or video pulled from a webpage - usually with a link crediting your site. It solves the searcher's problem on the spot and can boost your click-through rate, which is why getting featured in it is worth optimizing for.
organic-results
Organic results
The unpaid listings on a results page. Unlike ads, you earn these by being relevant - that is what SEO and AEO work toward.
serp
SERP (Search Engine Results Page)
The page of results a search engine shows after someone searches. The higher your business appears on it, the more people see you.
search-engine
Search engine
The website where people type questions and get results - Google and Bing are the big two. It works by ranking pages and showing them as a list of links.