How to Enrich Jotform Submissions with Clearbit and Upsert into Pipedrive Using Make.com

Introduction

You collect leads with Jotform and someone manually looks up the company on LinkedIn or Clearbit before creating a Pipedrive contact. That manual enrichment is slow and inconsistent. You want reliable, repeatable enrichment so sales gets richer records and you avoid wasted outreach.

This guide shows how to enrich Jotform submissions with Clearbit in Make.com, then upsert the resulting person and organization into Pipedrive with idempotency and audit logging. By the end you will have a repeatable pattern that turns raw form data into actionable CRM records and notifies your sales channel.

What you will learn: the Make.com modules to use, where to map Clearbit fields into Pipedrive, how to prevent duplicates, and the small gotchas that cause bad data in production.

What You'll Need

• Jotform account with the form you accept submissions from (webhooks enabled, paid plan may be required for advanced features)
• Clearbit account and API key with Enrichment access (person and/or company enrich endpoints)
• Pipedrive account with permission to create and update Persons and Organizations
• Make.com account to orchestrate the scenario (intermediate use of routers, HTTP modules, and error handlers; paid plan recommended)
• Google Sheets (or Make Data Store) for idempotency and audit logs
• Slack workspace and bot token for notifications (optional but recommended)

Permissions and notes:

• Clearbit calls cost per lookup. Add a rule to only enrich when you have at least an email or company domain to avoid wasted calls.
• Pipedrive custom fields require exact keys; create any custom properties you plan to populate before mapping.

How It Works (The Logic)

Trigger: new Jotform submission. Make.com receives the payload, normalises email and company domain, checks an idempotency store, calls Clearbit to enrich person or company data when available, then searches Pipedrive for an existing Person by email and Organization by domain or name. If found, update; if not, create Person and Organization and associate them. Finally, write an audit row to Google Sheets and notify Slack for qualified leads.

In plain steps: Jotform → normalize → idempotency check → Clearbit enrich → Pipedrive search → create or update person/org → log → Slack notify.

Step-by-Step Setup

1. Design your Jotform fields and enrichment rules

• Require email where possible. If email is not available, require a company domain or company name to justify a Clearbit Company lookup.
• Keep labels simple: first_name, last_name, email, company, website, job_title, message, budget, region.
• Decide enrichment policy: only call Clearbit Person Enrichment when you have an email; call Clearbit Company Enrichment when you have a company domain or company name.

Gotcha: Clearbit works best with a canonical company domain. If the form collects "Company" only, add a small normalisation step to extract domain where possible (for example, from website field or email domain).

2. Create the Make.com scenario and webhook

• Module 1: Webhooks > Custom Webhook (Catch hook). Create the webhook and paste the URL into Jotform's webhook settings.
• Fetch a sample submission to capture payload shape.

Fields to extract immediately: response_id, submitted_at, email, full name, company, website, job_title.

3. Normalise identifiers and build idempotency key

• Module 2: Tools > Set variable. Create:

  • normalized_email = lowercase(trim(email))
  • company_domain = extract domain from website or from email (split on @) when website is missing
  • submission_key = response_id or form_id + response_id

• Module 3: Google Sheets > Search rows (idempotency). Search for submission_key.

  • If found and status is succeeded, stop. If found and status = processing, route to an ops alert for manual inspection. If not found, append provisional row with status = processing and continue.

Why: this prevents duplicate runs when Jotform retries webhooks or Make replays runs.

4. Conditional Clearbit enrichment

Add a Router with two branches:

• Branch A (Person Enrich): if normalized_email present → Call Clearbit Person Enrichment.
• Branch B (Company Enrich): if company_domain present → Call Clearbit Company Enrichment.
• Branch C: neither present → continue without enrichment (map only raw form fields).

Clearbit call details in Make.com:

• Module: HTTP > Make a request (unless Clearbit has a native connector). Use GET https://person.clearbit.com/v2/combined/find?email={email} or GET https://company.clearbit.com/v2/companies/find?domain={domain} depending on API.
• Set Authorization: Bearer {CLEARBIT_API_KEY} and Accept: application/json.

Parsing: parse JSON and map fields you care about (company name, domain, logo, sector/industry, employee count, person title, LinkedIn, linkedin_handle, twitter handle). Keep mapping narrow; too many fields create noise.

Gotcha: handle 404 responses gracefully. Clearbit returns 404 when it cannot find enrichment data; treat that as a valid empty response and continue.

5. Search Pipedrive for existing Person and Organization

• Module: Pipedrive > Search Persons by email (if email exists). Route accordingly.
• Module: Pipedrive > Search Organizations by domain or exact name (use the company domain or enriched company name). If your Pipedrive has a custom domain field, prefer domain search to avoid duplicates.

Routing logic:

• If Person found, capture person_id and go to update path.
• If Person not found but Organization found, go to create Person and associate with org_id.
• If neither found, create both Organization (if you have a company name/domain) and Person.

Gotcha: Pipedrive fuzzy matching can return close names. Prefer exact domain match when available to avoid creating a second org for the same company.

6. Upsert mapping rules

Update path (Person exists):

• Module: Pipedrive > Update Person. Map only non-empty incoming fields to avoid blanking richer CRM values.
• Map Clearbit fields selectively:
  • job_title → title
  • person.linkedin.handle → custom property linkedin
  • company.name from Clearbit → do not overwrite org name unless blank

Create path (Person not found):

• Module: Pipedrive > Create Person. Map:
  • name = Form full name or first + last
  • email → email array
  • phone → phone
  • job_title → title
  • custom fields: clearbit_job_title, clearbit_twitter, clearbit_person_richness (simple boolean)

Organization upsert:

• If you have a domain or company name, create or update an Organization with:
  • name = company name (prefer Clearbit company.name when available)
  • domain = company_domain
  • industry = clearbit_sector or clearbit_industry
  • employee_count = clearbit_metrics.employees

Always associate person_id with org_id after create.

7. Audit logging and finalise idempotency row

• Module: Google Sheets > Update Row. Update the provisional audit row with:
  • submission_key
  • final action (created/updated)
  • person_id
  • org_id
  • clearbit_status (person_found/company_found/none)
  • run_status = succeeded
  • timestamp

This sheet is the ground truth for reprocessing and compliance.

8. Slack notification for qualified leads

Add a filter to notify Slack only when the submission or Clearbit enrichment meets your qualification rules, for example:

• clearbit_metrics.employees > 50 and budget > threshold
• or job_title contains "Head", "Director", "VP"

Module: Slack > Send message to #sales or #ops. Keep it short and include the Pipedrive person link and a one-line enrichment summary.

Example message: "Hot lead: Jane Doe, Acme Corp (120 employees), jane@example.com — Matched via Clearbit. Link: "

9. Error handling

• For Clearbit 429 or rate-limit responses, implement exponential backoff with retries in Make.com. Log any permanent 4xx errors into the audit row error_message and set run_status = error.
• For Pipedrive 5xx errors, retry with backoff. If retries fail, set run_status = error and post to #ops with submission_key and a link to the provisional sheet row.

Common operational rule: do not auto-retry enrichment indefinitely. If Clearbit fails repeatedly, mark the run to continue without enrichment and notify ops. This keeps your CRM flowing.

Real-World Business Scenario

A B2B services firm used this flow to enrich inbound consultancy requests. Before automation, SDRs spent time researching each company and returned incomplete CRM records. After implementing this Make.com scenario, every Jotform submission with an email or domain got a Clearbit lookup where available. High-fit companies were auto-notified in Slack, and enriched Pipedrive records included company size and sector. The team reduced research time per lead by 70 percent and the CRM had significantly richer ownerable records.

We implemented a similar Jotform to Pipedrive upsert pattern in our guide on connecting forms to Pipedrive, which is a useful reference for basic mapping and dedupe ideas: see our walkthrough on how to Connect Jotform to Pipedrive and Auto-Create Contacts Using Make.com. For a focused look at upsert patterns, also see How to Push Jotform Submissions into Pipedrive Using Make.com.

Common Variations

• Replace Google Sheets with Make Data Store for higher-throughput idempotency and concurrency control.
• Run Clearbit only for submissions that meet a cheap ruleset first to reduce enrichment costs, for example budget > X or company size hint present.
• Add a human approval gate: queue enriched but high-value submissions into a Slack review channel where an ops user can approve before creating the Pipedrive Deal.

A practical wrap-up

You built an intermediate Make.com workflow that enriches Jotform submissions with Clearbit, then upserts persons and organisations into Pipedrive with idempotency, mapping rules, logging, and Slack notifications. If you want us to implement and harden this exact pattern for your team, Olmec Dynamics builds these automations for businesses and can help tune Clearbit usage and Pipedrive mappings. See what we do at Olmec Dynamics: https://olmecdynamics.com