HubSpot via Vimkit

Webflow forms capture submissions and send email notifications, but a submission sitting in a form dashboard is not a contact record. Teams running HubSpot alongside Webflow want each submission written straight into the CRM, with a bad email address caught before the visitor leaves the page.

Two routes do that today. The native HubSpot app in the Webflow Marketplace connects native Webflow forms to HubSpot and also handles HubSpot iframe and code embeds. Vimkit is a free third-party connector, built before that app existed, that validates field values against HubSpot's API while the visitor is still looking at the form.

For most teams the native app is the place to start, because Webflow has reviewed and approved it and it tracks HubSpot's current form editor. Vimkit earns its place in narrower cases: a HubSpot tier below Marketing Professional, or a Webflow-styled form that has to reject an invalid email domain on screen rather than after the post. Marketing operations people and agency builders working inside a client's HubSpot account are the readers who usually land there.

How to integrate HubSpot via Vimkit with Webflow

What is HubSpot via Vimkit? Vimkit is a free form connector run by Jensa Ventures that sends native Webflow form submissions to HubSpot. It installs as one site-wide script plus one custom attribute per form, validates the submitted values against HubSpot's API first, and works with HubSpot's free tier as well as paid ones.

Check what state Vimkit is in before you build on it. Everything testable from outside still answers as of July 2026, including the dashboard login and the runtime script the snippet loads onto your site. Vimkit's own site tells the other half of the story, with a copyright that stops at 2022, help articles that still point at retired Webflow University URLs, and a homepage now gated behind an early-access request. Treat it as working but unmaintained, and keep the native app as your fallback.

Vimkit itself documents two ways to register a form, and a third option sits outside Vimkit entirely. The snippet and custom attribute method covers the normal case, while the HubSpot embed code fallback covers accounts where nobody can grant OAuth access. For sync requirements past what Vimkit does, a direct API build against Webflow and HubSpot gives you full control at the cost of server-side work.

Compare the native HubSpot app with Vimkit

The two routes differ on validation timing, HubSpot plan requirements, and how far you can trust each one to keep working. This table lays out the tradeoff.

Read the table top to bottom and the decision is usually made for you. Where your HubSpot subscription supports the native app's form editor features, use it, and reach for Vimkit when you need HubSpot's rules to fire in front of the visitor on a form you styled in Webflow.

Connect Webflow forms with the Vimkit snippet and custom attribute

The main method installs one script site-wide and then tags each form with an attribute. You paste Vimkit's snippet into your head code, connect HubSpot over OAuth, and map a form. Granting that OAuth access requires Super Admin rights on the HubSpot account, and the snippet goes into the field described in Custom code in head and body tags.

To set up the integration:

1. Create a free Vimkit account, then add your website in the dashboard to generate a snippet. Enter the domain or subdomain only, with no folder or page path, and pick Production if you run a single environment.
2. In Webflow, open Site settings > Custom code and paste the snippet into the Head code field.
3. Publish the site, then click Verify in Vimkit to confirm the snippet is live.
4. In Vimkit, click Connect Hubspot Account, sign in, and click Grant Access. Vimkit lists the forms in the account so you can pick one.
5. Back in Webflow, select the Form element rather than the Form block, open Element settings > Custom attributes, and paste the name and value pair Vimkit gives you.
6. Enter the full URL of the page holding the form, click Verify, then publish and submit a test entry.

Once the form is registered, Vimkit takes over four jobs:

• Real-time validation: Submitted values go through HubSpot's API first, so a check such as an MX lookup can reject an email domain that does not exist.
• Field mapping: Webflow form fields land in the matching HubSpot fields and CRM properties, which is why the field names have to be identical on both sides.
• Native styling: The form on the page stays a Webflow form with your own classes, so no HubSpot iframe or external stylesheet is involved.
• Visitor context: HubSpot records the sequence of page visits and submissions behind each contact, which Vimkit's product page notes works on the free tier too.

Build the HubSpot form with the same field names as the Webflow one before you start, since a mismatch is the most common reason a submission arrives empty. You also need a paid Webflow account or an active Site plan to add custom code at all, which Vimkit states as a prerequisite. Test one form on a published Collection list template before you roll the attribute across every Collection page.

Add a HubSpot form with its embed code

When nobody on the team has HubSpot Super Admin rights, skip the OAuth step and register the form by hand. This is the usual path for an agency building inside a client's HubSpot account, and Vimkit documents it in its embed code article.

To register a form manually:

1. Copy the form's embed code from HubSpot.
2. In Vimkit, click Add Form, then Add the form manually, paste the embed code, and click Add Form.
3. If you want the HubSpot form itself on the page, drop the embed code into a Code Embed element from the Add panel.

A Code Embed is custom code as well, so the same paid-plan requirement applies and nothing else changes on the Webflow side by taking this route.

Build with the Webflow Data API and HubSpot APIs

Vimkit publishes no API of its own, so anything past its documented scope means calling both platforms yourself. Attribution you can audit, or a sync that also writes Webflow CMS items, belongs in this category. The Webflow API and HubSpot's APIs cover the pieces:

• HubSpot Forms API: The form submission endpoint takes a POST to /submissions/v3/integration/submit/{portalId}/{formGuid} on https://api.hsforms.com and accepts up to 1,000 fields per request.
• HubSpot CRM contacts: The contacts API guide covers creating and updating contact records outside the forms flow.
• Webflow form submissions: Webflow exposes stored submissions through its submissions endpoint, which is useful for backfilling anything a live connection missed.
• Webflow webhooks: A registered webhook pushes each form_submission event to your own endpoint as it happens.

Most custom builds chain that webhook straight into the HubSpot Forms API.

Forward form submissions with a Webflow webhook

This sub-method skips Vimkit and gives you control over exactly what reaches HubSpot, which suits teams that owe someone an attribution guarantee or need processing in between.

To implement it:

1. Register the webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks using the form_submission trigger type, which needs the sites:write scope.
2. Read the event on your endpoint. The payload reference shows a data object of submitted key-value pairs alongside a schema array listing each field's fieldName, fieldType, and fieldElementId.
3. Forward the fields to the HubSpot submission endpoint. If you captured the visitor's hubspotutk cookie, pass it in context.hutk so HubSpot attaches the submission to that visitor's history.

HubSpot access tokens last 30 minutes, so store the refresh token and rotate as described in the OAuth quickstart guide. If attribution matters and you stay on the Vimkit path instead, confirm with a test submission that the hubspotutk value reaches HubSpot before you count on the contact timeline.

What you can build with the HubSpot via Vimkit Webflow integration

Vimkit is worth the setup where a Webflow-designed form has to behave like a HubSpot form, with the CRM record and the validation both arriving without a middleware subscription. These are the setups it fits.

• Trial signup with routing fields: A signup form maps company size and timeline into custom CRM properties, so high-value prospects reach sales without a manual review step.
• Gated content on a free HubSpot tier: An early-stage team collects downloads into HubSpot contacts before it has a Marketing Professional subscription to justify.
• Client intake for agency builds: An agency registers a client's HubSpot form by embed code, keeping the Webflow styling while the client keeps Super Admin control of its own account.
• Appointment and inquiry capture: A booking or property inquiry form creates the contact and starts a HubSpot workflow, with invalid-email rejections happening on the page instead of in your CRM.

Before you commit to any of these, walk through the native HubSpot app setup and see whether it already covers your case, then fall back to Vimkit for the gaps it genuinely fills.