Blog

Sending Form Submissions to HubSpot Without Building an Integration

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.

← Back to the blog
AI Powered

Explore this article with AI

Get an instant summary, key takeaways, action items, and answers to your questions about this article.

Choose your AI assistant
ChatGPT Perplexity
Quick answer

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 setup, start to finish

The connection lives on the individual form, not the whole account, which keeps it predictable. From the form's dashboard:

  1. Go to Settings → Integrations.
  2. Click Connect next to HubSpot and authorize access to your HubSpot account. Authorization happens through HubSpot's own screen — there are no API keys to copy or paste.
  3. Map each FormBridge field (for example fb-sender-email) to the HubSpot contact property it should update. This is done once per form.
  4. Submit a test entry and check the contact in HubSpot.

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.

Get the mapping right the first time

A one-time mapping is a strength, but it also means a wrong choice quietly affects every future lead.

One form, one purpose

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.

Don't let junk reach the CRM

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.

When Zapier is still the right answer

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.

Frequently asked

Do I need an API key to connect HubSpot?

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.

Can different forms sync to different HubSpot properties?

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.

What happens if the same person submits twice?

The submission updates the existing contact rather than creating a duplicate, as long as the email address is mapped so HubSpot can match it.

Key facts

  • The HubSpot connection is set up per form under Settings → Integrations, using OAuth rather than API keys.
  • Field mapping is done once per form and applies to every later submission.
  • Each submission creates a new HubSpot contact or updates an existing one, matched on email.
  • The HubSpot integration is available on the Pro plan and up.

Terms in this post

Contact property
A field on a HubSpot contact record, such as email, name or a custom property you define.
Field mapping
The one-time match between a form field and the CRM property it should fill.
OAuth
An authorization method where you approve access on the other service's own screen instead of sharing a secret key.

Get the next one in your inbox.

One email when we publish something worth reading. No spam — appropriately enough, we'd know.