How to Build Lead Capture Pipelines Across Typeform, HubSpot, and Salesforce

March 4, 2026

Lead capture is the starting point for most customer acquisition workflows. Prospects fill out forms on landing pages, event registrations, demo requests, or surveys. That data then needs to flow into CRM systems where sales and marketing teams can follow up.

Many SaaS products build features that ingest leads from forms and push them into systems like HubSpot or Salesforce. The challenge is that form providers and CRMs all expose different APIs, schemas, and authentication models. Integrating Typeform, Google Forms, HubSpot, and Salesforce individually quickly becomes complex to maintain.

Unified simplifies this process by providing normalized APIs for both Forms and CRM platforms. Developers can retrieve form submissions and write leads into CRM systems using consistent objects and endpoints, enabling reliable lead capture pipelines across many providers.

Why SaaS Products Need Lead Capture Pipelines

Lead capture pipelines are common in many SaaS products, including:

• Marketing automation platforms
• Customer data platforms
• RevOps tools
• Event and webinar platforms
• AI lead qualification products

These products ingest leads from form platforms and route them to CRM systems so that sales teams can follow up.

A typical lead pipeline involves:

• Form submissions from platforms like Typeform
• Lead enrichment or validation in the application
• CRM record creation in HubSpot, Salesforce, or other systems
• Automated routing to sales representatives

Building this pipeline reliably requires consistent access to both form submission data and CRM write endpoints.

Common Lead Capture Workflows

Lead capture pipelines typically support several workflows.

Landing page lead capture

Marketing teams collect contact information from demo request or newsletter forms.

Event registrations

Conference or webinar registrations are submitted through forms and routed to CRM systems.

Product sign-up forms

Applications capture new users and create corresponding CRM leads.

Qualification surveys

Prospects submit information about company size, budget, or use case through structured forms.

Lead enrichment pipelines

Submitted data is enriched before being pushed into CRM systems.

Unified Categories Used in Lead Capture Pipelines

A lead capture pipeline typically connects two Unified API categories.

Using normalized APIs across these categories allows developers to ingest leads from many form providers and route them into CRM systems without writing vendor-specific integrations.

Unified Objects and Key Fields

Unified standardizes the core objects required to build lead pipelines.

Forms Objects

Each form contains a list of fields, which define the questions presented to the user.

CRM Objects

These CRM objects allow applications to create or update customer records when new leads are captured.

Connecting Form Providers and CRM Systems

Customers authorize their form platforms and CRM systems through Unified Connect.

Typical flow:

1. Your application launches the Unified Connect authorization component.
2. The user selects integrations such as Typeform, HubSpot, or Salesforce.
3. The user authorizes access to their account.
4. Unified redirects back to your application with a connection_id.

Your application stores the mapping:

user_id → connection_id

All subsequent API requests use the connection_id to retrieve submissions or write CRM records.

Retrieving Form Submissions

Form submissions are retrieved through the Forms API.

List forms

GET /forms/{connection_id}/form

Retrieve a form

GET /forms/{connection_id}/form/{id}

List submissions

GET /forms/{connection_id}/submission

Retrieve a single submission

GET /forms/{connection_id}/submission/{id}

Submissions contain structured data including:

• respondent identifiers (respondent_email, respondent_name)
• submission timestamps (created_at)
• the associated form (form_id)
• an array of responses (answers)

The answers array contains each response submitted by the user.

Each answer includes:

• field_id
• field_name
• value

This structure allows developers to extract and transform form responses for CRM ingestion.

Mapping Form Responses to CRM Leads

When building a lead pipeline, form responses must be mapped to CRM fields.

A typical mapping process includes several steps.

Identify the lead

Use the submission fields:

• respondent_email
• respondent_name

These values often correspond directly to CRM lead fields.

Match answers to form questions

Each answer includes a field_id. This identifier matches the corresponding question in the form definition.

By retrieving the form schema, developers can determine:

• question label
• field type
• validation rules

Convert values based on field type

Different form field types map to different CRM fields.

Examples:

• TEXT or TEXTAREA → CRM notes or text fields
• EMAIL → lead email field
• PHONE → phone number field
• NUMBER → numeric CRM field
• SINGLE_SELECT / MULTIPLE_SELECT → CRM picklists or tags
• FILE_UPLOAD → attachments

Track submission metadata

Include submission metadata such as:

• created_at for lead capture time
• form_id to associate leads with campaigns

Because Unified normalizes form structures across providers, the same mapping logic works across Typeform, Google Forms, and other supported platforms.

Writing Leads to CRM Systems

Once submissions are mapped to CRM fields, the application can create or update lead records.

Example CRM write endpoints include:

POST /crm/{connection_id}/lead
POST /crm/{connection_id}/contact

These endpoints allow developers to create new leads or contacts directly in systems like HubSpot or Salesforce.

Applications can also update existing CRM records.

PUT /crm/{connection_id}/lead/{id}
PUT /crm/{connection_id}/contact/{id}

This allows pipelines to update leads with additional information or enrichment data.

Data Flow for Lead Capture Pipelines

A typical lead ingestion pipeline follows this pattern.

1. Connect integrations

Customers authorize their form platform and CRM through Unified Connect.

2. Retrieve form definitions

Fetch forms and field definitions to understand the question schema.

3. Ingest submissions

Retrieve form submissions using the Forms API.

4. Map responses to CRM fields

Transform submission answers into structured lead data.

5. Create CRM records

Use CRM write endpoints to create new leads or contacts.

6. Store data locally

Persist normalized records in your database for analytics or reporting.

Real-Time Lead Capture with Webhooks

Unified supports webhook events for form submissions.

The primary events include:

• form.created
• form.updated
• submission.created

The most important event for lead capture pipelines is submission.created, which fires whenever a respondent completes a form.

Applications can subscribe to this webhook and trigger lead creation immediately when new submissions occur.

This allows pipelines to process leads in real time rather than polling APIs repeatedly.

Supported Platforms

Unified supports a wide range of form and CRM integrations.

Form integrations

Examples include:

• Typeform
• Google Forms
• Tally

CRM integrations

Unified's CRM API supports 47+ CRM integrations, including:

• Salesforce
• HubSpot
• Pipedrive
• Zoho CRM
• Microsoft Dynamics 365
• Copper
• Close

This allows lead capture pipelines to support many customer environments without building separate integrations.

Why Product Teams Choose Unified

Building lead pipelines across form providers and CRM systems requires multiple integrations.

Unified simplifies this by providing:

• normalized APIs across forms and CRM platforms
• consistent data models for submissions and leads
• unified authentication flows
• webhook events for real-time ingestion

Instead of maintaining dozens of integrations, product teams can focus on building lead qualification, enrichment, and routing workflows.

Start building lead capture pipelines across Typeform, HubSpot, Salesforce, and many other platforms today.

→ Start your 30-day free trial

→ Book a demo