How to Push Typeform Submissions into Pipedrive Using Make.com

Introduction

You get Typeform responses and someone manually copies the data into Pipedrive, or you rely on the quick native connect and then fix duplicates and bad mappings later. That costs time and causes missed follow-ups.

This post shows a pragmatic Make.com scenario that receives Typeform submissions, normalises values, upserts a Person by email in Pipedrive, optionally upserts an Organization, creates a Deal when appropriate, and writes an audit row so you can troubleshoot problems quickly. By the end you will have a reliable pattern you can run in production.

What you will know by the end: exact trigger and modules to use in Make.com, field mappings, de-duplication logic, retry and error patterns, and Pipedrive v2 considerations.

What You'll Need

• Typeform account with webhooks enabled or a form accessible through Make.com
• Pipedrive account with API access and permissions to create/update Persons, Organizations and Deals
• Make.com account (recommended paid tier for execution limits and error handlers)
• Google Sheets (or Make Data Store) for idempotency/audit logging
• Slack workspace and an integration token for notifications (optional)

Notes on requirements: webhooks and reliable execution at scale usually require paid plans on Typeform and Make.com. For Pipedrive use an API token or OAuth client with least-privilege scopes.

How It Works (The Logic)

Trigger: new Typeform response. Make.com receives the payload, normalises email and other fields, checks the audit log to ensure the submission_id is not already processed, searches Pipedrive for a Person by email, then either updates the Person or creates a new Person and associated Organization. Optionally create a Deal when the submission qualifies, then write the outcome to Google Sheets and notify Slack on high-value leads.

In plain steps: Typeform submission → idempotency check → search Person by email → update or create Person (+ Organization) → create Deal if needed → write audit row → notify Slack for qualified leads.

Step-by-Step Setup

1. Prepare your Typeform and mapping document

• Make email required on the form. Use stable question references or record the Typeform response_id.
• Decide which fields map to Pipedrive Person, Organization, Deal or custom fields. Document the mapping (Typeform question id → Pipedrive field key).

Common gotcha: changing Typeform question IDs mid-project breaks mappings. Lock the form or update your mapping when you change a question.

2. Create a new Scenario in Make.com and add the Typeform trigger

• Module: Typeform, "Watch responses" (webhook gateway). Select your form and fetch a sample payload.
• Pull response_id, email, full name, company, phone, and any qualifying fields (budget, interest level).

3. Normalise values and build idempotency key

• Tools: add a small mapping step to trim/ lower-case the email and create submission_key = response_id.
• Record the submission_key early so retries do not create duplicate records.

4. Idempotency check against Google Sheets or Make Data Store

• Module: Google Sheets, Search rows (or Data Store Get Item) by submission_key.
• If a row exists with status = succeeded or pending, stop the flow. If not, append a provisional row with status = processing and continue.

Why this matters: Typeform retries or accidental double submits will otherwise create duplicate People or Deals.

5. Search Pipedrive for existing Person by email (use v2 modules)

• Module: Pipedrive v2, "Find Person" or use the Search endpoint via HTTP if your connector requires it.
• Use the normalised email.
• If a Person exists, capture person_id and current properties. If not, continue to the create branch.

Pipedrive v2 note: Pipedrive is moving to v2 webhooks and API flows. Build against v2 modules in Make.com to avoid a future migration. See Pipedrive's migration guidance when you plan long-term maintenance.

6. Route: Update existing Person or Create new Person and Organisation

Route A (Person found)

• Module: Pipedrive v2, "Update Person". Map only non-empty incoming fields to avoid overwriting better existing values.
• If company name is present, optionally search Organization by name; if found, link the person; if not, create Organization and link.

Route B (Person not found)

• Module: Pipedrive v2, "Create Person". Map:
  • email → email
  • first and last name or full name → name fields
  • phone → phone
  • any custom Typeform fields → matching Pipedrive custom properties
• After person creation, upsert Organization if company is present and associate it.

Common gotcha: Pipedrive dropdown/custom fields require exact option keys. If you map user-visible labels, ensure they match the Pipedrive option labels or keys exactly.

7. Create a Deal when the submission meets your criteria

• Add a conditional step: if interest_level == "high" or budget >= threshold, create a Deal in the appropriate pipeline and stage, linking it to person_id and org_id.
• Map deal title to something informative, e.g., "Lead: {{company}} — {{name}}" and set value if budget is provided.

8. Append audit row and mark completion

• Module: Google Sheets, Append Row. Write: submission_key, typeform_id, email, action (created/updated), person_id, org_id, deal_id (if any), run_status, timestamp, any error message blank.
• Then update the provisional row with run_status = succeeded.

9. Notifications and error handling

• On success for qualified leads, post a Slack message in your sales channel with the person name, email, company and link to the Pipedrive Person. Keep the message short and actionable.
• Implement an Error handler sub-scenario in Make.com that captures 4xx/5xx responses, retries transient errors with exponential backoff, writes failures to Google Sheets, and posts to an ops channel when retries exceed your threshold.

10. Test end-to-end and monitor

• Submit tests covering: new email creates Person; re-submission with same email updates Person; submission that triggers Deal creation; missing email routes to manual review.
• Monitor Make.com execution logs for the first 48–72 hours and spot-check Google Sheets audit rows for any anomalies.

Real-World Business Scenario

A B2B recruitment agency used this flow to capture candidate referrals and client enquiries. Before automation, staff manually entered contacts and created deals, which introduced duplicates and delayed outreach. After implementing this Make.com scenario with email upserts and a Deals-on-high-intent rule, they cut manual admin by 70% and reduced duplicates because resubmissions merged into existing Persons.

They also added Slack alerts only for high-value deals so recruiters did not get spammed by low-priority submissions.

Common Variations

• Use a Lookup table to route submissions into different Pipedrive pipelines or owners based on the Typeform answer for region or service type.
• Add enrichment (Clearbit or company lookup) between the Person search and create steps to populate organization fields before creating a Deal.
• Replace Google Sheets with an internal database or Make Data Store for higher volume idempotency and better concurrency control.

Production notes and Pipedrive v2 guidance

Pipedrive is migrating webhooks and API functionality to v2, with v1 scheduled for retirement. Build new scenarios using Pipedrive v2 modules in Make.com. If you have legacy v1 scenarios, plan a migration and test mappings before the v1 sunset.

If you want deeper examples of Typeform lead patterns and mappings, see our guide on integrating Typeform with HubSpot for upserts and enrichment, available as a related walkthrough. For a similar Pipedrive form pattern built from Jotform, you can reference our Jotform to Pipedrive example for field mapping ideas.

If you prefer, Olmec Dynamics can build and harden this exact flow for your forms and Pipedrive setup. See what we build in our Typeform to HubSpot guide for related patterns and mapping examples or our Jotform to Pipedrive post for Pipedrive-specific choices. For the HubSpot guide, read "How to Connect Typeform to HubSpot and Auto-Create New Leads Using Make.com" (https://olmecdynamics.com/news/typeform-hubspot-new-lead-sync-make-com). For the Jotform pattern, see "How to Connect Jotform to Pipedrive and Auto-Create Contacts Using Make.com" (https://olmecdynamics.com/news/connect-jotform-to-pipedrive-make-com).

Putting this into action

You just built a production-ready pattern to move Typeform submissions into Pipedrive with Make.com, using email-based upserts, organization sync, optional deal creation, audit logging, and robust error handling. If you want this implemented or extended to match your Pipedrive pipeline and custom fields, Olmec Dynamics builds and maintains integrations like this for teams that need reliable CRM ingestion. Visit Olmec Dynamics to see how we help teams ship dependable automation: https://olmecdynamics.com