Guides

Webflow Forms for B2B Lead Capture: Native, HubSpot or Custom, With Spam and Attribution Handled

How to run lead forms on a Webflow site in 2026: what native Webflow forms include, when a HubSpot form is the better choice, when to post to your own endpoint, and how to keep spam out and UTMs in.

Summarize with AI
Octo Agency cover: Webflow Forms for B2B Lead Capture, with a purple hexagon pattern

Every paid Webflow site plan includes unlimited form submissions, native bot blocking and spam filtering at no extra charge, while the free Starter plan stops collecting after 50 submissions for the life of the site (Webflow pricing page and Help Center, opened 7 November 2026). That is the first fact to know about Webflow forms, because most complaints about them come from a site still on the free plan, or from a form whose custom action silently bypasses everything Webflow does.

This guide covers the three ways to run a lead form on a Webflow site, what each does with spam and attribution, and the launch test we would run first. Every limit comes from Webflow's, HubSpot's, Google's or Cloudflare's own documentation.

What Webflow forms do natively, and where the native path stops

A Webflow form is an ordinary HTML form that Webflow's servers process on submit. Each form can send its submission to several destinations at once: Webflow's store, email notifications, a webhook, or an app such as HubSpot, Zapier or Make. The exception is the custom action, which posts the form straight to a URL you choose, skips Webflow's processing, and cannot be combined with the others.

What a native Webflow form includes, by site plan
CapabilityStarter (free)Basic ($15/mo)Premium ($25/mo)
Submissions50 in total, never resetsUnlimitedUnlimited
Notification recipients5, all Workspace membersAny addressesAny addresses
File uploadNoNoYes, 10 MB per file
CSV export and spam inboxYesYesYes
Webhook, Apps, custom actionYesYesYes
Custom domainNoYesYes

Source: Webflow pricing page and Help Center, read 2026-11-07. Prices are billed yearly.

The store and the inbox. Submissions sit under Site settings > Forms, one table per form, with CSV export. With spam filtering on, suspected spam goes to a separate spam inbox rather than disappearing. Name every form: the default is "Email Form", and two unnamed forms share one table.

Notifications. Each form has its own recipients, sender name, reply-to, subject and body, with variables for the form data. Webflow recommends a named mailbox over admin@ or info@, because role addresses are filtered more often. An unbranded sender address needs a Growth Workspace.

Webhooks. A form can post to one or more webhook URLs. Each request carries an x-webflow-signature header, a SHA-256 HMAC you verify with the secret Webflow shows once at creation. Anything other than a 200 is retried three more times at ten-minute intervals, then dropped; a webhook that keeps failing is deactivated.

Where native stops. Webflow validates required fields and input types, but has no conditional logic, multi-step state or routing, and nothing native writes to a CRM on its own. That is what the app, webhook or custom action is for.

Three ways to run a lead form on a Webflow site

For a B2B marketing site the choice is between a native Webflow form, a HubSpot form, and a native form posting to an endpoint you own. We build marketing sites in Webflow, so read our view with that bias.

Native Webflow form vs HubSpot form vs custom endpoint
QuestionNative Webflow formHubSpot form in WebflowCustom endpoint
Where the lead landsWebflow store, email, webhook or appHubSpot contact recordWherever you send it
Who styles itWebflow DesignerHubSpot editor, or CSS with a Professional planWebflow Designer
Spam layerreCAPTCHA v2, bot blocking, spam filteringHubSpot's own filteringTurnstile or reCAPTCHA, your rules
UTM captureHidden fields, passed to webhooks and most appsHidden fields on the HubSpot formAnything you read from the URL or cookies
Running costSite plan onlyHubSpot plan; Professional for developer embedA small serverless function
Fits whenContact, newsletter, gated contentHubSpot is the system of record and marketing owns the formsRouting, enrichment, consent logic or two systems of record

Source: Webflow Help Center, HubSpot Knowledge Base, Cloudflare Turnstile plans, read 2026-11-07.

The native form. The default for a contact page, a newsletter box and a gated download. Build it in the Designer, name it, point it at a webhook or an app, and add the spam layers below. Our post on Webflow apps a B2B marketing team needs covers which apps carry form data.

The HubSpot form. When HubSpot is the system of record, a HubSpot-built form avoids a mapping step: fields are contact properties, hidden fields read URL parameters such as utm_campaign into properties, and the submission carries the visitor's tracking cookie. The cost is styling. The standard embed is styled in HubSpot's editor; the developer code that lets you style it with your own CSS needs a Marketing Hub or Content Hub Professional or Enterprise subscription. The site's domain must also be added to HubSpot's tracking settings, or its submissions are marked as spam. Our HubSpot Webflow Integration guide covers the four connection paths in detail.

The custom endpoint. A native Webflow form with a custom action pointed at a small server you run, or a Webflow webhook feeding the same server. It is the right answer when a lead has to be enriched, routed to a territory, written to two systems, or checked against a consent rule before anyone sees it. Of the two wirings we would prefer the webhook: Webflow's store, notifications, spam settings and retries stay in the path, and a lead stored in two places beats a lead stored in none. The custom action is only needed when the server has to decide what the visitor sees next.

Spam: four layers, what each one costs

Webflow's Help Center lists four spam methods: CAPTCHA, bot blocking, spam filtering and the honeypot. Two of the four are a toggle.

Spam layers available on a Webflow site
LayerHow it is enabledWhat it doesVisible to the visitorCost
Bot blockingSite settings > Apps & Integrations > Cloudflare Turnstile spam protectionAnalyses mouse movement and inputs, blocks bot submissions on every formSubmit button disabled while the check loadsIncluded
Spam filteringSame setting, second toggleChecks submitted data, routes spam to the spam inboxNoIncluded
reCAPTCHA v2 checkboxreCAPTCHA element in each form plus keys under Apps & IntegrationsGoogle challenge before submitYes, a checkboxFree to 10,000 assessments a month per organisation
HoneypotHidden field plus custom codeDiscards submissions where a bot filled the hidden fieldNoDeveloper time
Turnstile on a custom endpointWidget in the form, siteverify on your serverCloudflare challenge, usually invisibleRarelyFree, 20 widgets per account

Source: Webflow Help Center, Google Cloud reCAPTCHA pricing, Cloudflare Turnstile plans, read 2026-11-07.

Two rules follow from Webflow's documentation. First, reCAPTCHA validation is site-wide: once the keys are saved, every form without a reCAPTCHA element fails to submit, immediately, whether or not you republish. Second, Webflow supports only the v2 "I'm not a robot" checkbox; v3 keys produce an "Invalid site key" error.

What the free tier covers. Google gives 10,000 reCAPTCHA assessments a month free per organisation, then a flat $8 for 10,001 to 100,000 and $1 per 1,000 above that. A single site rarely reaches the paid band; an agency pooling many clients under one Google organisation can.

Our order of operations. We would turn on bot blocking and spam filtering on every site at launch, since both are free and invisible, and add reCAPTCHA only where spam continues. On a custom endpoint we would use Turnstile: free for up to 20 widgets with 10 hostnames each, a checkbox shown only to risky visitors in managed mode, and a server-side check that is one POST to siteverify with a token that lives 300 seconds and verifies exactly once.

Attribution: getting the campaign from the URL to the CRM

A form that works but loses its UTM values is the most expensive failure: the paid campaign keeps spending with no credit. Where the values end up depends on the path.

Native form to webhook or app. Add hidden inputs for utm_source, utm_medium, utm_campaign, gclid and the landing page, fill them from the URL or a first-touch cookie with a few lines of custom code, and they travel with the submission.

Native form to HubSpot's non-HubSpot forms tool. This is the path the HubSpot app uses for native Webflow forms, and it has hard rules: static HTML present at page load, an email input of type email, a standard submit button, no iframe, no single-page app, no JavaScript bound to submit. The rule that bites: "The form must not contain hidden fields. The tool does not collect information from any hidden fields." Your UTMs have to arrive another way, for example through a parallel webhook. HubSpot also records a submission for every click of the submit button, including ones that fail validation.

HubSpot form. Hidden fields on a HubSpot-built form do capture URL parameters into contact properties, with one restriction: a required field cannot be hidden, and the pre-populate option for returning visitors can overwrite a hidden value.

Custom endpoint to HubSpot's Forms API. The unauthenticated submission endpoint takes the portal ID and form GUID in the path, up to 1,000 fields, and a context object with the hutk tracking cookie, page URI and page name. Pass hutk and HubSpot ties the submission to the visitor's existing timeline.

Measuring the form itself. GA4's enhanced measurement adds form_start, fired the first time a visitor interacts with a form in a session, and form_submit, with the parameters form_id, form_name, form_destination and form_submit_text. Those parameters only appear in reports once you create custom dimensions for them, so do that before launch. Our analytics stack for a four-week build covers the rest.

Field count and friction: what the data says

Zuko's benchmark across 321,937 contact-form sessions puts completion at 47.4%, with desktop at 51.2% and mobile at 39.4%; lead generation forms, which Zuko labels enquiry forms, sit at 42.7%. The desktop-to-mobile gap is the number to act on: test the form on a phone with the keyboard open, use the phone input type so the numeric keypad appears, and keep labels outside the fields, since placeholders disappear on typing and are not read by screen readers.

The field count debate is covered in our web form conversion statistics post, and our demo request conversion rates post shows top-performing demo forms converting about as well with thirteen fields as with two. Ask for what sales will use in the first call; the hard questions belong in the CRM or a booking step.

A launch checklist for a Webflow form

  1. The site is on a paid site plan, or the 50-submission cap is monitored under Site settings > General.
  2. Every form has a unique name and its own notification recipients at a named mailbox, with reply-to set to the submitter's email.
  3. Bot blocking and spam filtering are on, and the submit button's disabled state is styled.
  4. If reCAPTCHA is on, every form has the element, and the keys are v2 checkbox keys registered for the custom domain and the webflow.io subdomain.
  5. Hidden attribution fields exist, and the path that carries them was chosen with the HubSpot hidden-field rule in mind.
  6. A test submission from a UTM-tagged URL on the published site shows up in the CRM with the campaign attached, in GA4 as form_submit, and in the inbox.
  7. The webhook signature is verified, and file uploads, if used, have "Restrict uploaded file access" set deliberately, since by default only people logged into Webflow can open the link.

What this means for a B2B team choosing a form path

Start native. A named Webflow form with bot blocking, spam filtering and a webhook covers a contact page, a newsletter and a gated asset, costs nothing beyond the site plan, and keeps a copy of every lead in Webflow's store. Move the form into HubSpot when marketing owns the forms and HubSpot is the system of record, and budget for a Professional plan if it must match the design exactly. Build a custom endpoint when a lead needs routing, enrichment or two destinations, fed by Webflow's webhook so the native store and retries stay in the path. The launch test is always the same: one submission from a UTM-tagged URL, traced to the CRM. Our Webflow development service page explains how we scope forms, tracking and integrations inside a four-week build.

Frequently asked questions

Are Webflow forms free?

Forms are included in every Webflow site plan. On the free Starter plan a site can collect 50 submissions in total, a limit that never resets, and notifications go to at most five Workspace members. Every paid site plan, from Basic at $15 a month billed yearly, includes unlimited submissions, CSV export, webhooks and app connections. File upload needs Premium at $25 a month (Webflow pricing and Help Center, November 2026).

How do I stop spam on Webflow forms?

Turn on bot blocking and spam filtering under Site settings > Apps & Integrations > Cloudflare Turnstile spam protection; both apply to every form and route suspected spam to a spam inbox. If spam continues, add a reCAPTCHA element to every form and enable v2 checkbox validation, remembering that forms without the element then fail to submit. On a custom action form Webflow's settings no longer apply, so use Turnstile on your endpoint (Webflow Help Center).

Do Webflow forms work with HubSpot?

Yes, in three ways: HubSpot's non-HubSpot forms tool captures native Webflow forms on any HubSpot plan, a HubSpot form can be embedded, or a server can post to HubSpot's Forms API. The catch on the first path is that HubSpot does not collect hidden fields, so UTM values stored there are lost. The embed's developer code, needed for full CSS control, requires a Marketing Hub or Content Hub Professional or Enterprise plan (HubSpot Knowledge Base, 2026).

Can Webflow forms send data to a webhook?

Yes. A form's Send to setting accepts one or more webhook URLs, and Webflow signs each request with an x-webflow-signature header, a SHA-256 HMAC of the timestamp and body, using a secret shown once at creation. A non-200 response is retried three more times at ten-minute intervals before delivery is dropped, and a webhook that keeps failing is deactivated. Each site allows up to 75 webhooks per trigger type (Webflow Developers, 2026).

How do I keep UTM parameters in Webflow forms?

Add hidden inputs for the UTM values and the click ID, fill them from the URL with custom code, and send the form to a webhook, an app that reads hidden fields, or your own endpoint. Do not rely on HubSpot's non-HubSpot forms tool for this, since it ignores hidden fields. If the form is HubSpot-built, its hidden fields read URL parameters into contact properties directly (HubSpot Knowledge Base). Test with a tagged URL on the published site before launch.

Sources

  1. Plans and pricing Webflow
  2. Form submissions Webflow Help Center
  3. How do I add forms in Webflow? Webflow Help Center
  4. Prevent spam in form submissions Webflow Help Center
  5. Add a reCAPTCHA element Webflow Help Center
  6. Working with webhooks Webflow Developers
  7. Use non-HubSpot forms HubSpot Knowledge Base, 2026
  8. Pass contact property values with hidden form fields HubSpot Knowledge Base, 2026
  9. Set up and style your form on an external site HubSpot Knowledge Base, 2026
  10. Submit data to a form (unauthenticated) HubSpot Developers
  11. Compare reCAPTCHA tiers Google Cloud
  12. Turnstile plans Cloudflare Docs
  13. Turnstile server-side validation Cloudflare Docs
  14. Enhanced measurement events Google Analytics Help
  15. Form type benchmarking Zuko

Tags

  • Webflow
  • Forms
  • Lead capture
  • Attribution
Mihajlo Stojanovic

Mihajlo Stojanovic

Co-founder, Octo Agency

Mihajlo runs the technical side of Octo Agency: Webflow builds, custom backends and the systems that keep a site editable after launch. He has shipped more than twenty Webflow sites a year as a white-label partner and writes about what survives contact with a real marketing team.

Veljko Nikolic

Reviewed by

Veljko Nikolic

Founder, Octo Agency

Veljko runs the build side of Octo Agency. He has shipped marketing sites for B2B teams in legal tech, health and manufacturing, and writes about what survives contact with a real review cycle.