1. Connect the accounts
Install the HubSpot App for the intended Webflow site, authorize access and connect the correct HubSpot account. Launch the app from the Designer’s Apps panel.
Forms and tracking setup
Webflow HubSpot Integration
Connect Webflow to HubSpot with the official app, choose a form method and test contact capture. This guide covers setup, tracking and common integration problems before considering a CMS migration.
Form setup
How to connect Webflow forms to HubSpot
Start with the official HubSpot App and choose the capture method before styling the form. Your choice determines which fields and editor controls are available.
2. Choose the form method
Use an iframe for a form managed in HubSpot, developer embed for more styling control when your plan supports it, or the app’s Webflow form option for native elements. Check field support before choosing native mapping.
3. Verify the result
Publish to staging and submit a test entry. Check destination fields, form errors, success state and mobile layout, then repeat the checks on the production domain.
The app’s documented native form option currently supports text inputs and requires non-HubSpot form capture enabled. Place HubSpot embeds inside a div or container rather than nesting them in a Webflow form block. See Webflow’s current HubSpot App instructions for the supported modes and requirements.
Tracking and updates
Keep form capture and site analytics aligned
Verify site tracking separately after connecting the form. Add the public domain in HubSpot tracking settings and avoid loading the same snippet through both custom code and another integration. After changing a developer embed form’s structure in HubSpot, refresh it in Webflow and test the revised fields.
Using an existing Webflow form
Inventory its field types and required values before replacing its submission route. Check whether Webflow still stores submissions, whether HubSpot receives the intended properties and whether retries produce unwanted records. Choose one agreed capture path for each form so troubleshooting has a clear starting point.
Integration QA
Troubleshoot the complete lead journey
Form missing or clipped
Check the published page, embed placement, container dimensions and browser errors. Test without an extension blocking scripts and repeat on a mobile device.
Contact or fields missing
Verify the account, form and property mapping. Check spam submissions and connector logs. Test one new contact and one repeat submission separately.
Visits or follow-up missing
Check tracking and consent independently from contact capture. Confirm the intended workflow or notification is available in your subscription and enabled for the tested event.
Use the official HubSpot external form guide for embed and domain requirements and the tracking installation guide for analytics checks.
Decision guide
When Webflow HubSpot integration is enough
Forms and contacts
Use integration when Webflow forms only need to create or update HubSpot contacts and trigger simple follow-up workflows.
Tracking and attribution
HubSpot tracking can support page views, submissions, and campaign reporting while the front-end remains in Webflow.
Separate site ownership
Integration works when the team is happy editing in Webflow and only needs HubSpot for CRM and marketing operations.
Migration trigger
When to migrate Webflow to HubSpot instead
If Webflow and HubSpot feel like two separate operating systems, integration may not solve the real problem. A Webflow to HubSpot migration is usually the better fit when marketers need pages, forms, reporting, and CRM context in one HubSpot-native setup.
Need help scoping the website handoff?
Share your current site and form requirements through the contact form, or explore the migration resources before deciding on a CMS move.