Typeform Contact Capture HubSpot Workflow Template

This n8n workflow handles Typeform lead capture and simple HubSpot follow-up.
- Receives a new Typeform submission in real time
- Maps submitted name, company, department, and email fields into a structured record
- Creates a new HubSpot contact from the form response
- Checks whether the person indicated interest in business services
- Updates interested contacts to the opportunity lifecycle stage in HubSpot
- Sends an email with next-step information only to interested contacts

This workflow captures a Typeform submission, converts the answer set into a cleaner contact structure, writes the record into HubSpot, and sends a follow-up email only when the lead shows interest. In practice, it works as a simple lead intake and routing layer between a marketing form and your CRM.

What goes into the workflow

The input is a live Typeform response. The JSON export shows the workflow pulling out first name, last name, company name, department, email address, and a boolean-style interest answer from the submitted form fields. Those raw answers are not sent directly into HubSpot. A Set step first remaps them into cleaner internal field names so later nodes can work with predictable values.

What comes out

The main output is a new HubSpot contact. If the interest condition is true, the same contact is moved to the opportunity lifecycle stage and receives an email with next-step material. If the lead does not match the interest condition, the workflow exits without additional outreach. That makes the output more selective than a simple form-to-CRM sync.

Where the automation logic matters

The key logic is the conditional branch between the initial HubSpot contact creation and the follow-up sequence. This is useful when every form response should be stored, but not every person should receive the same sales-facing email. The branch keeps the CRM complete while limiting outbound follow-up to leads that match the question logic from the form.

Required tools and setup

You need a Typeform account, HubSpot credentials, and Gmail access in n8n. You also need to review the exact Typeform field mappings because the exported workflow references the original question labels. If those labels change in your form, the Set node needs to be updated. The Gmail node also contains placeholder-style content that should be replaced with your actual meeting link, presentation link, or onboarding message.

Who should use this template

This template is a good fit for teams that already collect inbound leads through Typeform and want those responses inside HubSpot immediately. It is especially useful when you do not need complex scoring yet and only need one or two qualification conditions before sending a reply.

What usually needs customization

Most users will need to change the Typeform field mapping, the HubSpot field mapping, and the email copy. You may also want to add duplicate protection, UTM field capture, lead owner assignment, or list segmentation in HubSpot. If your intake logic depends on more than one answer, replace the single If branch with a richer scoring or routing step.

Common limitations

This workflow does not include deduplication, enrichment, or fallback handling for invalid email addresses. It also assumes your form structure stays stable. If the form changes often, a more defensive mapping layer is worth adding. If you need lead scoring, queueing, or SDR assignment, treat this template as the first stage of a larger CRM workflow rather than the final version.