How to Connect Jotform to Pipedrive and Auto-Create Contacts Using Make.com

Introduction

You still copy Jotform responses into Pipedrive by hand, or your sales team misses new prospects because someone forgets to create the contact. That slow handoff costs lead response time and creates duplicate or messy CRM records.

This guide shows a tight Make.com scenario that takes a Jotform submission, searches Pipedrive for an existing person by email, updates the contact if found, or creates a new person if not. It adds a Slack notification for qualified leads. By the end you will have a reliable, low-noise lead capture flow.

What you will know by the end: the exact Make.com modules to use, field mappings to apply, and the de-duplication trick that prevents duplicate people in Pipedrive.

What You'll Need

• A Jotform account with the form you want to use
• A Pipedrive account with permission to create and update people
• A Make.com account with Jotform and Pipedrive connections
• A Slack workspace and channel for notifications (optional but recommended)
• Access to API credentials or OAuth connections in Make.com for both Jotform and Pipedrive
• Note: Jotform webhooks and higher volumes may require a paid Jotform or Make.com plan

How It Works (The Logic)

Trigger: a new Jotform submission arrives. Make.com receives the submission, searches Pipedrive for a person by email. If a match exists, update that person with the new fields. If no match, create a new person and optionally create a deal. Finally, post a short Slack message for qualified leads.

Trigger → Search Pipedrive by email → Update or Create person → Optional deal creation → Slack notification

Step-by-Step Setup

1. Prepare your Jotform fields

Keep field labels simple: First Name, Last Name, Email, Company, Phone, Interest Level, Message. Make sure the email field is required. If you use hidden fields for campaign or source, include them now.

Common gotcha: optional email fields cause upstream failures. Make email required to make deduplication reliable.

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

Add the Jotform module named "Watch for New Submissions." Select your form and fetch a sample submission. Confirm the payload includes email and any hidden fields.

3. Add Pipedrive: Search for Person by Email

Add the Pipedrive module "Search Persons" or the equivalent search action in the connector.

• Use the submission email as the search term
• If the connector supports it, limit search to active persons

If the search returns a person, the scenario will continue on the update branch. If not, it will continue to the create branch.

Common gotcha: Pipedrive sometimes stores multiple contacts with the same email across organisations. Make sure your search priority matches your CRM practice.

4. Add a filter or router to branch on search results

Use a router with two routes:

• Route A: when the search returns at least one person ID
• Route B: when the search returns no results

This explicit branching makes the logic clear and easy to maintain.

5. Route A, update existing person

Add the Pipedrive "Update a Person" module and map fields from Jotform to Pipedrive person properties:

• First name → Name split or full name field
• Last name → if you split names
• Email → primary email (some connectors expect an array; map accordingly)
• Phone → phone field
• Organization name → map to Organization name if you use it
• Custom fields: map Interest Level or any UTM/hidden fields

If you want to append the message into a notes field, concatenate the existing notes with the new submission text.

Common gotcha: Do not blindly overwrite valuable CRM fields. Consider updating only when the incoming value is non-empty.

6. Route B, create a new person (and optional deal)

Add the Pipedrive "Create a Person" module and map the same fields as above.

If your process requires creating a deal for new leads, add the "Create a Deal" module and associate it with the returned person ID. Map deal title to something like "Lead: {{company}} — {{interest level}}" and set value if the form collects budget.

7. Add a Slack notification for qualified submissions

After both update and create branches, add a Slack "Post a Message" module into the same channel via a second router or by merging branches.

Send notifications only for qualified leads by adding a filter such as Interest Level equals "High" or Budget greater than a threshold. Keep the message short and actionable.

Suggested message format:

New lead from Jotform
Name: {{first_name}} {{last_name}}
Email: {{email}}
Company: {{company}}
Interest: {{interest_level}}
Pipedrive: <https://app.pipedrive.com/person/{{person_id}}|Open contact>

Gotcha: If your Pipedrive instance uses custom person URLs, construct the link using the returned person ID pattern specific to your account.

8. Optional: Deduplication safety in a spreadsheet

For very high volumes or race conditions, add a quick Google Sheets or Airtable lookup to record processed submission IDs. Before creating a person, check that the submission ID is not already processed. This prevents duplicates when multiple submissions arrive nearly simultaneously.

9. Test end-to-end

Submit several test entries including:

• A new email to create a person
• A second submission with the same email to update
• Submissions that trigger and do not trigger Slack notifications

Verify Pipedrive records update correctly and Slack messages include a working person link.

10. Turn the scenario on and monitor the first week

Watch Make.com execution logs for errors and any partial updates. In Pipedrive, spot-check newly created people to ensure fields map to the right properties.

Real-World Business Scenario

A small B2B agency used this exact flow to capture inbound consultancy enquiries. Before automation the sales lead owner spent 30 minutes per day copying form submissions into Pipedrive. After automation, every submission appeared in Pipedrive instantly, duplicates were avoided by email search, and the sales channel received only high interest notifications. That improved first response time and reduced CRM cleanup.

Common Variations

• Create a deal automatically for new high-budget leads.
• Add an enrichment step using a third-party API to append company data before creating the person.
• Route notifications to the account owner by matching company or region in a small lookup table.

Make this part of your stack

You now have a simple and reliable Jotform to Pipedrive flow built in Make.com that prevents duplicates and surfaces qualified leads to Slack. If you want this implemented or extended across your form, CRM, and notification stack, Olmec Dynamics builds these systems for real businesses. See our work connecting forms and CRMs in our post about Typeform and HubSpot for a similar pattern: How to Connect Typeform to HubSpot and Auto-Create New Leads Using Make.com. You can also compare scheduling handoffs and document generation patterns in our guides on Calendly to ClickUp and Google Docs PDF generation: How to Create ClickUp Tasks from Calendly Bookings Using Make.com and Slack and How to Generate a PDF from a Google Docs Template Using Make.com and Gmail.