Setup guide
From install to your first Webflow submission in HubSpot. It takes about 10 minutes. You need a published Webflow site with a form, and a HubSpot account with the form you want to fill. Webflow's free Starter plan takes only 50 form submissions in total, so use a paid Webflow site plan for a live site.
1. Connect Webflow
On the setup page, click "Connect Webflow". Webflow shows what the app asks for: read your sites and forms, and create the webhook that sends each form submission to us. Approve access for the site you want to use. You come back to the setup page. Connecting Webflow is also how you sign in: next time, click "Connect Webflow" again.
2. Connect HubSpot
Click "Connect HubSpot" and pick the HubSpot account your forms are in. HubSpot shows a notice that this app has not been reviewed by HubSpot yet, and may ask you to type "I accept the risk" to continue. This is HubSpot's standard notice for apps not yet listed in its marketplace. HubSpot may show it twice. The setup page then shows your HubSpot account id and where HubSpot hosts it (na1 or na2 for the US, eu1 for the EU).
3. Receive the site's form submissions
The setup page lists your Webflow sites. Click "Receive this site's form submissions" next to the site. From then on, Webflow sends each form submission on that site to us within a second. The free plan covers 1 site.
4. Pair a form and match the fields
Click "Pair a form" next to the site. Pick the Webflow form and the HubSpot form it should fill, then click "Next: match the fields".
For each Webflow field, pick the HubSpot field it fills, or "Do not send". Fields with the same name are picked for you. Every field type works: text, email, phone, number, text area, dropdown, radio buttons and checkboxes. If your Webflow form has one checkbox per option and HubSpot has one multiple-checkbox field, pick the option for each checkbox ("Interests: ads (checked)"); the checked ones are joined into one HubSpot value. Your Webflow field names never change.
Click "Save pairing". The setup checks page opens and lists anything that would lose a submission or send it twice, in plain words, with a link to fix it.
5. Turn off HubSpot's "Collect data from website forms"
If HubSpot's tracking code is on your Webflow site, HubSpot can collect your Webflow forms by itself ("non-HubSpot forms"). Then each submission reaches HubSpot twice: once from HubSpot's script and once from us. In HubSpot, go to Settings > Marketing > Forms > Non-HubSpot Forms tab and turn off "Collect data from website forms". Then click "I've turned it off" on the setup checks page. HubSpot does not tell apps whether this setting is on, so the page asks you.
The tab's address depends on where HubSpot hosts your account. After you connect HubSpot, our setup page shows your account id and where it is hosted, and this page shows your own link.
- US accounts (na1): https://app.hubspot.com/settings/<your HubSpot account id>/marketing/form/non-hubspot
- US accounts (na2): https://app-na2.hubspot.com/settings/<your HubSpot account id>/marketing/form/non-hubspot
- EU accounts (eu1): https://app-eu1.hubspot.com/settings/<your HubSpot account id>/marketing/form/non-hubspot
6. reCAPTCHA and spam
If CAPTCHA is on for the HubSpot form, HubSpot refuses submissions sent by apps like this one. In HubSpot, open the form, go to Options and turn off "Enable CAPTCHA". The setup checks page tells you when it is on. The spam protection on your Webflow form keeps running on your site.
Before sending, we check each submission for links and common spam words. A submission that looks like spam is held: it is not sent, it sends you no email, and it shows in the submission log with the reason. If it is not spam, click "Release and send". It is then sent without the visitor's HubSpot cookie, so it cannot merge into another contact.
7. Consent checkboxes
If your Webflow form has consent checkboxes, map each one on the field matching screen to "Consent: agrees to let you store and process their data" or "Consent: subscribes to" one of your HubSpot subscription types. In the consent text box next to it, paste the exact words the visitor sees next to the checkbox. HubSpot records those words as what the visitor agreed to. The setup checks page warns you when the HubSpot form asks for consent and no checkbox is mapped.
8. Optional: visit history
HubSpot can show which pages a visitor looked at before filling in your form. That needs a small script on your Webflow site. See Send visit history to HubSpot for the script and where to paste it.
9. Send a test submission
Publish your Webflow site, open the page with the form, and submit it with your own email. Open the submission log: within a minute it says "Sent to HubSpot.". In HubSpot, open the form's submissions: the test is there. If the log shows "held" or "failed" instead, the reason says what to change.
What the daily comparison and failure emails do
Every day, we compare the submissions Webflow kept for each paired form during the last day with the submissions HubSpot has. A submission HubSpot does not have is marked "missing" in the log. The same daily check looks at each site's Webflow webhook: Webflow turns a webhook off after deliveries fail several times, and we set it up again and say so in the log.
When a submission fails, is held or is missing, we email you once for that submission, with the reason and a link to the log. Spam holds send no email. Submissions held because the plan's monthly limit is used send one email a month, and they are sent as soon as you upgrade.
Resend a submission
In the submission log, missing, held and failed submissions have a Resend button. Fix the reason first (for example a required HubSpot field), then click Resend. Each submission is checked again before it is sent, and a submission HubSpot already has is never sent again.
Change or delete a pairing
On a pairing's setup checks page, click "Edit the pairing" to pick another HubSpot form or match the fields again, for example after you rename a field in Webflow or add a required field in HubSpot. "Delete the pairing" stops sending that form; its submissions stay in the log.