Form to HubSpot: Create Contacts and Deals Without Zapier

A HubSpot form integration should do one thing well: when someone submits a form, the right HubSpot Contact, Deal, and workflow should fire within seconds — not minutes, not after a Zapier poll, not after a third tool's queue clears. FlexForm connects directly to HubSpot's API, so a form submission creates a Contact, an associated Deal, and triggers any HubSpot workflow you've wired up — in 1–2 seconds, with no middleware in the path.

This guide walks through the exact configuration: how to connect HubSpot to FlexForm, how to map form fields to Contact and Deal properties, how to set conditional routing rules, and how to verify the submission landed correctly. The goal is a working form-to-HubSpot pipeline that you can ship today.

Why bypass Zapier for HubSpot

Zapier remains the default glue for SaaS tools, and for many workflows it is the right answer. For a form-to-HubSpot path, the trade-offs are different. A native integration writes the Contact directly to HubSpot's API the moment the submit button is pressed. A Zapier-based path queues the submission, polls the source, processes the trigger, and only then forwards to HubSpot — adding 1 to 15 minutes of latency depending on the Zapier plan.

For consumer surveys or backfill workflows, 5 minutes does not matter. For a B2B lead capture form where an SDR is supposed to respond inside a 5-minute SLA, a Zapier delay can consume the entire response budget before the rep ever sees the record. The Lead Response Management research from MIT and InsideSales is now 15 years old, but the conclusion still holds: contact within the first minute correlates with materially higher conversion.

The second trade-off is cost stacking. A Zapier-based form-to-HubSpot setup requires a form tool subscription plus a Zapier subscription with enough tasks to cover submission volume. FlexForm's Founders plan at $19/mo includes the HubSpot connection in-plan — there is no separate Zapier or Make line item.

Step-by-step: connect a form to HubSpot

The five-step path below assumes you already have a FlexForm account on the Founders plan or Enterprise. If you are still on Starter, native CRM integrations are not enabled — upgrade before continuing.

1. 1

   Generate the form

   Describe the form to FlexForm's AI: "Create a demo request form with name, work email, company, company size dropdown, primary use case, and a free-text question about current tools." FlexForm picks the field types (short_answer, email_input, dropdown, multiselect, long_answer) and assembles the form in under 60 seconds. Refine fields conversationally if needed — the Founders plan includes refine and regenerate.

2. 2

   Connect HubSpot via OAuth

   In the form's Integrations panel, click Connect HubSpot. You'll be redirected to HubSpot to authorize FlexForm's scopes (contacts read/write, deals read/write, workflows trigger). After approval, FlexForm stores the connection at the workspace level — every form in the workspace can reuse the same HubSpot connection without re-authorizing.

3. 3

   Map fields to Contact properties

   FlexForm auto-suggests mappings based on field labels: email_input maps to HubSpot's email property, short_answer for "Full name" maps to firstname + lastname. Review each mapping and add custom Contact properties from your HubSpot portal — FlexForm pulls the live property list, including custom fields. Existing Contacts are matched by email and updated; new emails create new Contacts.

4. 4

   Configure Deal creation

   Add a Deal action alongside the Contact action. Choose the pipeline (Sales, Customer Success, or any custom pipeline), the initial stage (typically "New Lead" or "Qualification"), the dealname template (e.g., "{Company} — Demo Request"), and the deal amount if your form captures budget via a currency element. The new Deal is associated with the Contact automatically using HubSpot's association API.

5. 5

   Add conditional routing (optional)

   If your form has company-size or use-case fields, configure conditional rules: company_size = 'Enterprise' → assign Contact owner to the enterprise SDR, route Deal to the Enterprise pipeline. Conditions use FlexForm's branching syntax (equals, contains, is_empty) and evaluate inline at submission. No additional zap, no second tool.

Field mapping in practice

The default field-to-property mapping covers most cases, but every team has custom HubSpot properties — lead source codes, account tiers, regional flags. FlexForm pulls the live HubSpot property list per connection, so any custom property created in your portal becomes available as a mapping target without re-syncing or re-authenticating.

For workflows where one form serves multiple use cases (e.g., a single contact form that can be either sales or support), use a dropdown element at the top of the form and conditionally set HubSpot properties downstream. The submitted dropdown value can set hs_lead_status to one of multiple values, which in turn fires the appropriate HubSpot workflow.

Triggering HubSpot workflows

Most teams that connect a form to HubSpot want the submission to start something — a welcome sequence, a sales notification, a task assignment. In HubSpot, workflows are triggered by enrollment criteria, typically based on a Contact or Deal property value.

The cleanest pattern is: have FlexForm set a HubSpot property called form_source to a value like demo_request_v3 on every submission. In HubSpot, create a workflow with enrollment trigger "form_source equals demo_request_v3" — the workflow will fire on every matching submission, with the full Contact and Deal context available inside it.

This decouples FlexForm and HubSpot in a healthy way: FlexForm owns the form and the property write, HubSpot owns the workflow logic. Marketing can adjust the sequence inside HubSpot without touching the form, and form owners can ship new variants by changing the form_source value.

FlexForm direct vs Zapier-mediated

Verifying the integration

After configuration, run three checks before exposing the form publicly:

1. Test submission: Submit the form with a unique test email (e.g., test+1781032525886@yourdomain.com). Confirm the Contact appears in HubSpot within 2 seconds and that all mapped properties are populated.
2. Deal association: Open the new Contact in HubSpot. The associated Deal should appear in the Deals tab with the correct pipeline, stage, and dealname. If the Deal exists but is not associated, check the association object in field mapping.
3. Workflow firing: If you configured a property-based workflow trigger, check HubSpot's workflow history. The new enrollment should appear within seconds, with the test Contact correctly enrolled.

If any of these fail, FlexForm logs the integration result on the submission record itself — you don't need to hunt through a separate tool's history. Failed HubSpot writes show the exact API error message inline. Web embed instructions are covered separately once the integration is verified.

When to stay on Zapier

Native HubSpot integration is the right default for new form-to-HubSpot pipelines. There are still cases where Zapier earns its keep:

• You need to fan a single submission out to HubSpot and three or four other tools that FlexForm doesn't natively support (e.g., a legacy internal CRM, a custom database).
• Your team's automation lives in Zapier and you want a single source of truth for "what happens on form submit."
• You're prototyping and don't want to commit to a Founders plan yet — Zapier can connect any form to HubSpot at the cost of latency, while you validate the workflow.

For the common case — lead capture, demo request, contact us, customer feedback — native is faster, simpler, and cheaper to operate. The migration path is straightforward: rebuild the form in FlexForm, configure the HubSpot connection, switch your embed code, then retire the zap.

Frequently asked questions