CRM integration
Jotform HubSpot integration guide for service businesses
Learn how to connect Jotform to HubSpot CRM so a quote request, consultation form, or intake form becomes a usable contact, deal, task, and follow-up record. This guide shows when the direct Jotform HubSpot integration is enough and when Make is the better layer for routing service inquiries.
Quick answer
Connect Jotform to HubSpot directly for simple capture. Add Make when the route branches.
The strongest first setup is usually Jotform collecting the request and HubSpot storing the lead. That is enough when every submission should create the same contact, company, deal, or ticket. Add Make only when the workflow needs filters, branching, duplicate checks, alerts, or different next steps by service type.
- Use Jotform + HubSpot directly when one form should create or update one CRM record.
- Add Make when qualified, maybe-fit, and no-fit requests need different routes.
- Do not automate yet if the business has not defined what makes an inquiry worth fast follow-up.
- Track source page so later affiliate and SEO decisions can be based on useful leads, not just visits.
Workflow route
How to send Jotform leads to HubSpot CRM.
The goal is not to create a clever integration. The goal is to make every qualified inquiry visible in the CRM with a clear next action.
Collect the service request
Use Jotform for the front-door quote request, consultation form, project intake, or file-heavy request that needs more structure than a basic contact form.
Create or update the contact
Send name, email, phone, company, service type, and request summary into HubSpot so the lead does not live only inside form notifications.
Create the deal or task
If the submission is sales-ready, create a deal, ticket, or task with the request context and a clear next action for the operator.
Route exceptions separately
Use Make or HubSpot workflow rules when some requests need a fast alert, some need a clarification email, and some should be tagged as no-fit.
Field mapping
Map only fields that help follow-up.
| Jotform field | HubSpot destination | Why it matters | Guardrail |
|---|---|---|---|
| Name | Contact name | Personalizes follow-up and CRM records | Split first and last name if the CRM setup expects it |
| Email and phone | Contact methods | Lets the operator choose the right reply channel | Require at least one reliable contact method |
| Service type | Deal pipeline, lead status, or custom property | Routes the inquiry to the right next step | Use controlled options before relying on free text |
| Project details | Deal notes, contact note, or ticket description | Gives context before the first response | Keep long text readable in alerts and tasks |
| Timing or urgency | Task due date, priority, or deal property | Helps urgent qualified requests get faster attention | Do not let every visitor mark every request urgent |
| Budget range | Deal amount or qualification property | Separates strong-fit requests from mismatch | Allow "not sure" when exact budget would reduce good leads |
| Source page | Original source detail or custom lead source property | Shows which SEO pages create useful inquiries | Keep naming consistent across forms and pages |
Direct vs Make
Choose the integration layer by the routing problem.
Direct Jotform to HubSpot
Best when the form has a predictable path and every complete submission should add or update a contact, deal, company, or ticket in HubSpot.
Lowest setup complexityJotform to HubSpot through Make
Best when different service types, locations, budgets, or lead quality levels need different CRM actions, alerts, or reply paths.
Best for branching workflowsHubSpot form instead
Best when the form is simple and the business wants the whole capture and follow-up path to stay inside HubSpot.
Best when Jotform is not neededSetup checks
Test with real-looking submissions before relying on it.
- Submit a qualified request and confirm the HubSpot contact is created or updated.
- Confirm the deal, ticket, or task lands in the correct pipeline or view.
- Submit the same email twice and check whether duplicates are handled correctly.
- Confirm service type, urgency, budget, and project details remain readable in HubSpot.
- Confirm the source page is captured so future SEO pages can be judged by lead quality.
- Submit one no-fit request and make sure it does not trigger the same urgent route.
- Check where failed integrations will be noticed before a real lead gets missed.
If the workflow only needs clean CRM capture, start with the direct Jotform HubSpot integration. If the route needs branching, alerts, or handoffs across multiple tools, use Make as the connection layer.
Build the form with Jotform Route with MakeRelated guides
Build the rest of the intake route.
Source notes
Official pages checked for this guide
Integration features and plan limits change. Check official documentation before building a production intake workflow.