MigrateToAstro
Start a project

HubSpot with Webflow

HubSpot wants to own the form. Webflow wants to own the design. The right setup depends on the page: sometimes an embedded HubSpot form is best, and sometimes a Webflow form should post to HubSpot behind the scenes.

Start a project

HubSpot integrations like this usually take 2–4 days

Choosing the setup

Which form owns the submission.

A HubSpot form, embedded

  • HubSpot owns the form and its supported behavior
  • Progressive profiling and smart fields
  • A change made in HubSpot reaches the site without republishing it
  • Styling control goes with it, unless it is a developer embed

Right when the form's own behavior is the point

A Webflow form, posted to HubSpot

  • Webflow owns the markup and the interaction
  • The design and the validation stay native
  • Values sent behind the scenes, with the attribution written deliberately
  • Bounded by the field types the chosen route supports

Right when the design is the point

None of these is the wrong answer, and I pick per form rather than per site, on what the fields, the validation, the tracking and the styling actually need.

How it works

How the handoff works.

  1. 01

    Submit

    The form posts

  2. 02

    Contact

    New contact created, or an existing one updated

  3. 03

    Attribution

    Source and campaign checked

    Key handoff

  4. 04

    Workflow

    Configured workflows triggered

  5. 05

    Verify

    Contact details and routing confirmed

Why this is the key handoff

A success state only proves the browser thinks the form worked. I check that the contact arrived carrying its first touch and campaign, and that the workflow meant to handle it actually ran, because a workflow cannot add back what was never captured.

Before you wire it

Three things that commonly go wrong.

  1. 01

    Hidden fields on a scripted form arrive empty

    Where a framework controls the form, values written into the DOM can disagree with what that framework thinks is there, and HubSpot receives its version. The contact is created, the campaign arrives blank, and every visible part of the path succeeded, which is why the check is on the saved record.

  2. 02

    Embedded forms can need extra styling

    A HubSpot form embed carries HubSpot's markup. Making it match the site means overriding styles you do not control, which is fine until they change them.

  3. 03

    The form and the visitor tracking are separate installs

    One creates contacts, the other supplies the page views and attribution behind them, so each needs its own check. A contact can arrive successfully while its browsing history or attribution stays incomplete, and the tracking route depends on a script that a blocker or a conflict can stop from loading.

What you are buying

What is included.

  • Webflow forms creating or updating HubSpot contacts and deals

  • HubSpot forms embedded where progressive profiling or smart form behavior matters

  • Lifecycle stage, lead source, campaign and custom properties

  • HubSpot tracking code on the Webflow domain

  • Conversion events and form success behavior

Other integrations

Wire up something else?

Reach out and see if we are a good fit.

Start a project

Currently booking two to four weeks out.