If you're using Jotform for lead capture, client intake, or quote requests and manually copying submission data into HubSpot, this guide is for you.
The integration between Jotform and HubSpot is one of the most common workflow automation projects we handle. It's also one of the highest-leverage: once it's running, every form submission enters HubSpot correctly - without anyone touching it. No copy-paste. No missed records. No delay between submission and CRM update.
This guide covers the three main approaches to connecting Jotform with HubSpot, when to use each, and what to watch out for.
What you're trying to achieve
Before picking an integration approach, be clear on what you actually need. Most Jotform-to-HubSpot integrations fall into one of these patterns:
Contact creation or update. Every submission creates a new HubSpot contact if the email doesn't exist, or updates the existing contact if it does. This is the minimum viable integration for lead capture.
Deal or ticket creation. In addition to the contact, a deal (sales pipeline) or ticket (service pipeline) is created. Common for quote request forms, service intake, and application forms.
Property mapping. Specific form fields map to specific HubSpot contact or deal properties - budget, service type, company size, and so on. This is what makes the CRM record useful to the team working the lead.
Workflow triggers. Once the contact or deal exists in HubSpot, a HubSpot workflow fires - enrollment in a sequence, assignment to a rep, internal notification, or a task creation.
Knowing which of these you need determines which integration approach makes sense.
Approach 1: Jotform's native HubSpot integration
Jotform has a built-in HubSpot integration widget that handles basic contact creation and field mapping directly. This is the right starting point for most teams.
How to set it up:
- Open your Jotform form in the form builder.
- Go to Settings → Integrations and search for HubSpot.
- Authenticate with your HubSpot account using OAuth.
- Map your Jotform fields to HubSpot contact properties. At minimum, map email address - this is the identifier HubSpot uses to match existing contacts.
- Save and publish.
What it handles well: New contact creation, basic field mapping to standard HubSpot contact properties, and deduplication by email.
Where it falls short: The native integration doesn't create deals or tickets. It doesn't support conditional logic (e.g., only send to HubSpot if a specific field equals a specific value). And custom HubSpot object properties sometimes require workarounds. If your needs go beyond basic contact sync, move to Approach 2 or 3.
Approach 2: Zapier or Make as middleware
For more complex requirements - deal creation, conditional routing, multi-step sequences - using Zapier or Make as middleware gives you significantly more control.
Zapier setup:
- Create a new Zap. Set the trigger as Jotform → New Submission.
- Add a HubSpot action: Create or Update Contact. Map your Jotform submission fields to HubSpot properties.
- Add a second HubSpot action if needed: Create Deal or Create Ticket, associating it with the contact from step 2.
- Add filters or conditional paths if you only want certain submissions to flow through.
Make (formerly Integromat) setup:
Make gives you more granular control and is worth using if your logic involves multiple branches, error handling, or data transformation. The structure is similar: Jotform module as the trigger, HubSpot modules for each downstream action.
What middleware adds that native doesn't:
- Conditional logic: only create a deal if the budget field exceeds a threshold, or only trigger the sequence if the service type matches specific values
- Data transformation: concatenate fields, format dates, strip whitespace before sending to HubSpot
- Multi-action: create the contact, create the deal, send a Slack notification, and log to a Google Sheet - all from one submission
- Error handling: retry on failure, notify on error, log failed submissions separately
Cost consideration: Zapier and Make both charge based on task volume. For low-volume forms (under a few hundred submissions per month), the free tiers often cover it. High-volume forms will incur costs - factor this in before choosing middleware over a direct integration.
Approach 3: Cloudflare Workers or custom webhook
For teams with a developer on hand or for high-volume scenarios where Zapier/Make costs are prohibitive, a custom webhook handler gives you full control with no per-task cost.
Jotform supports webhook notifications - on every submission, Jotform sends a POST request to a URL you specify with the full submission payload as JSON or form-encoded data.
A Cloudflare Worker (or any serverless function endpoint) can receive that payload, transform the data, and call the HubSpot API directly to create contacts, deals, or whatever objects you need.
This approach is more work upfront but has no ongoing per-submission cost and no rate limits from a third-party middleware tool. It's the right call for forms with thousands of monthly submissions or for workflows with complex logic that would be expensive and brittle to build in Zapier.
The field mapping step: where most integrations break
Regardless of which approach you use, the field mapping step is where most Jotform-to-HubSpot integrations fail in practice.
The most common problems:
Email isn't mapped correctly. HubSpot uses email as the primary deduplication key for contacts. If your email field isn't mapped, HubSpot will create a new contact with every submission and your CRM will fill up with duplicates.
Custom HubSpot properties don't exist yet. If you're mapping a form field like "Preferred service type" to a HubSpot contact property called "Service Interest," that property needs to exist in HubSpot before the integration runs. Create your custom properties in HubSpot first, then set up the mapping.
Dropdown values don't match. If your Jotform dropdown says "Small business (1–50 employees)" and your HubSpot property expects "Small Business," the value won't populate correctly. Either normalize the values in the form, transform them in middleware, or use internal values in Jotform that match HubSpot's expected strings exactly.
File uploads don't carry over. Jotform can collect file attachments, but most integrations only pass text fields. If you need uploaded documents in HubSpot, you'll typically need a custom solution to fetch the file from Jotform's storage and attach it to the HubSpot record.
Testing before you go live
Before pointing a live form at the integration, test it thoroughly:
- Submit a test entry with a new email address. Confirm the contact was created in HubSpot with the correct field values.
- Submit a second test entry with the same email address. Confirm the existing contact was updated rather than duplicated.
- Submit a test entry that should trigger conditional logic (if you have any). Confirm the condition fires correctly.
- Check HubSpot's activity log for the test contact. Confirm all mapped fields are populated as expected.
If anything is wrong, fix it before sending real submissions through. Cleaning up a CRM full of duplicates or incorrectly mapped records is significantly more work than testing carefully upfront.
What to build on top of the integration
Once your Jotform submissions are landing cleanly in HubSpot, the integration becomes the foundation for the rest of your follow-up workflow:
HubSpot workflows. Enroll new contacts in a sequence automatically. Assign leads to reps based on property values. Create follow-up tasks on a schedule. These all fire from the contact record that your Jotform integration created.
Deal pipeline automation. Move deals through stages based on form responses, set close dates, and trigger internal alerts when high-value leads come in.
Reporting. With submissions entering HubSpot as structured records, you can start tracking form-to-close conversion, lead source performance, and pipeline velocity - none of which is possible when intake lives in an email inbox.
If your Jotform-to-HubSpot integration isn't working the way you expect, or you're starting from scratch and want to make sure it's set up correctly the first time, a Workflow Review is the right first step. Request one here - we'll look at your specific setup and tell you exactly what needs to change.
