Every Webflow form submission in HubSpot, or the reason it isn't

How it works

1. Connect Webflow and HubSpot. Approve access on Webflow's and HubSpot's own pages. Connecting Webflow is also how you sign in.
2. Pair a form. Click "Receive this site's form submissions", then pick the Webflow form and the HubSpot form it should fill. Fields with the same name are matched for you. Your Webflow field names never change.
3. Check the setup and send a test. The setup checks page lists anything that would lose a submission or send it twice. Submit your form once, and the log says "Sent to HubSpot."

Why it exists

• HubSpot can accept a submission and drop part of it. When an email address is not valid, or a dropdown value is not one of the form's options, HubSpot still answers OK and leaves the value out. FormFerret reads the HubSpot form before each send and holds a submission that would lose data, with the reason.
• Submissions can stop arriving with no error anywhere. FormFerret logs every submission and emails you when one fails. Once a day it compares the submissions Webflow kept with the ones HubSpot has, and marks any that are missing.
• Some connections send text fields only. Then dropdown, radio button and checkbox values never reach HubSpot. FormFerret sends text, email, phone, number, text area, dropdown, radio button and checkbox fields.
• Visit history gets lost. HubSpot links a contact to the pages they viewed through a cookie in the visitor's browser. An optional script copies that cookie into the form, so the submission arrives with it. Submissions are sent from our server, so they still arrive when an ad blocker stops the cookie, just without the visit history.

What you get

• A log of every submission. When it came in, the form, the visitor's email, the status and the reason, with HubSpot's error type and correlation id when there is one.
• Retries. When HubSpot is busy or down, the submission is sent again, up to 8 tries over about 1.3 hours. Each submission is sent to HubSpot once, even when Webflow sends it to us twice.
• An email when one fails. One email per submission that fails, is held or goes missing, with the reason and a link to the log. Fix the reason, then click Resend.
• Spam handling. A submission with a link or a common spam word is held, not sent, and sends you no email. If it is not spam, click "Release and send".
• Field matching for every field type. Pick the HubSpot field for each Webflow field. Separate Webflow checkboxes can fill one HubSpot multiple-checkbox field. Consent checkboxes go to HubSpot as consent, with the words you copy from your form.
• Setup checks. Warnings in plain words when CAPTCHA on the HubSpot form would block submissions, when a required HubSpot field gets no Webflow field, or when HubSpot may be collecting the same form a second time.