Get the next one in your inbox.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.
Connect a form to HubSpot once, map the fields, and every submission creates or updates a contact. What to map, what to avoid, and how to keep junk out of your CRM.

Get an instant summary, key takeaways, action items, and answers to your questions about this article.
Open the form's Settings → Integrations, click Connect next to HubSpot, authorize with OAuth (no API keys), and map each form field to a HubSpot contact property once. After that every submission creates a new contact or updates an existing one. Map email carefully and filter spam first so your CRM stays clean.
Getting a lead from a website form into a CRM has traditionally meant a tool in the middle, a webhook receiver, or a developer. If your goal is simply "every contact-form submission becomes a HubSpot contact", you can skip all of it.
The connection lives on the individual form, not the whole account, which keeps it predictable. From the form's dashboard:
fb-sender-email) to the HubSpot contact property it should update. This is done once per form.From then on, each new submission creates a contact or updates an existing one. The step-by-step version lives on the HubSpot integration page.
A one-time mapping is a strength, but it also means a wrong choice quietly affects every future lead.
Because the connection is per form, different forms can map to different HubSpot properties — or skip HubSpot entirely. That is a feature: a sales enquiry form can sync to your CRM while a careers form or a support form stays out of it. Plan your forms around where each submission should end up, then let routing decide who gets notified.
Everything that syncs into HubSpot becomes something your sales team has to look at, and contacts created from spam can distort your lists and reports. Turn on spam filtering and a honeypot or CAPTCHA on the form before you connect it, not after the first hundred bad records.
A direct connection covers the common case: create or update a contact. If you need something more elaborate — creating a deal, notifying a different team, or touching several tools after one submission — the Zapier integration can pick up where the direct HubSpot connection stops. The two work side by side.
No. You authorize through HubSpot's own screen from the form's Settings → Integrations tab, so there are no API keys to copy or paste.
Yes. The connection and the field mapping live on each form, so one form can map to a different set of properties than another, or not sync to HubSpot at all.
The submission updates the existing contact rather than creating a duplicate, as long as the email address is mapped so HubSpot can match it.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.