H
·6 min read

How to Enrich Pipedrive Leads with Clearbit Using Make.com

Enrich Pipedrive leads with Clearbit via Make.com, auto-fill company data, apply a lead score, log results to Google Sheets, and notify sales in Slack.

Introduction

Enrich Pipedrive leads with Clearbit automatically so your sales team sees company size, industry, and tech signals the moment a contact is created. Right now someone opens LinkedIn, looks for company size and role, and types notes into the CRM. That manual lookup costs time and adds variability to qualification.

This post shows a practical Make.com build that listens for new Pipedrive people or deals, queries Clearbit person and company endpoints, writes results back into Pipedrive custom fields, applies a simple lead score, logs the enrichment in Google Sheets, and posts a Slack alert for high-value prospects. By the end you will have a repeatable workflow you can deploy across your sales intake.

What you will know by the end: the Make.com modules to use, Clearbit endpoints to call, field mappings into Pipedrive, and the de-duplication and audit steps that keep the flow reliable.

What You'll Need

  • A Pipedrive account with API access and permission to create or update People and Deals
  • A Clearbit account with an API key for Person and Company Enrichment (Clearbit requires a paid plan for sustained volume)
  • A Make.com account (paid plan recommended for webhook reliability and higher operation counts)
  • A Slack workspace and channel for sales notifications (optional, but recommended)
  • A Google Sheets file for a simple enrichment audit log (optional, recommended for tracing)
  • Permission to create custom fields in Pipedrive for company size, industry, tech signals, enrichment status, and lead score

How It Works (The Logic)

Trigger: a new Pipedrive person or deal is created. Make.com captures the new record. If the record has an email, Make.com calls Clearbit Person Enrichment, then calls Clearbit Company Enrichment using the domain parsed from the email. Make.com maps Clearbit attributes into Pipedrive custom fields, computes a simple lead score, writes the score and enrichment status back to Pipedrive, appends an audit row in Google Sheets, and posts a Slack alert for leads above your score threshold.

In short: New Pipedrive person → Clearbit person lookup → Clearbit company lookup → Map fields to Pipedrive → Score → Log → Slack notify.

Step-by-Step Setup

  1. Plan Pipedrive custom fields

Create these custom person or deal properties in Pipedrive before you build:

  • company_size (single choice or number)
  • industry (text)
  • company_domain (text)
  • clearbit_enriched (single choice: pending, success, failed)
  • lead_score (number)
  • tech_signals (text)
  • enrichment_notes (text)

Naming consistency matters. Use short property keys you can map cleanly in Make.com.

  1. Start a new Scenario in Make.com and add the Pipedrive trigger

Use the Pipedrive module "Watch Persons" or "Watch Deals" depending on whether you want to enrich people or deals. Set the trigger to fire on creation. Add a second manual-run route for re-enriching records flagged as failed.

  1. Add a filter to ensure an email exists

Add a Make.com filter so the flow continues only when the person has a valid email. Clearbit needs an email or domain. If the email is missing, use the Pipedrive update module to set clearbit_enriched to failed with a short note.

  1. Parse domain from email

Use Make.com text functions to extract the domain from the email address and store it as company_domain. If the domain is a generic provider like gmail.com, skip the company enrichment branch and only attempt person enrichment.

Gotcha: personal email domains often return no company data. Mark those records person-only so reps know what was attempted.

  1. Call Clearbit Person Enrichment

Add an HTTP module to GET https://person.clearbit.com/v2/people/find?email={{email}} with header Authorization: Bearer <CLEARBIT_KEY>. Handle 200 responses by mapping useful fields, and handle 404 gracefully.

Map person attributes into Pipedrive fields or enrichment_notes:

  • employment.role → job_title or enrichment_notes
  • name.fullName → verify or update the contact name
  • bio or social handles → enrichment_notes

If person data exists but company lookup fails, set clearbit_enriched to person-only.

  1. Call Clearbit Company Enrichment

If domain is non-generic, call https://company.clearbit.com/v2/companies/find?domain={{company_domain}}. Map the response to Pipedrive:

  • metrics.employees or metrics.employeesRange → company_size
  • category.industry → industry
  • site.title or description → enrichment_notes
  • Any tech signals from the response into tech_signals

Set clearbit_enriched to success when company data maps into Pipedrive.

  1. Apply a simple lead scoring rule

Compute lead_score inside Make.com using a small weighted rule. Example:

  • +30 if employees > 200
  • +20 if industry is in your target list
  • +20 if tech_signals include your product keywords
  • +10 if the person role indicates seniority (CEO, Head, Director)

Keep this rule transparent and easy to tweak later.

  1. Update Pipedrive record with enrichment and score

Use the Pipedrive module "Update a Person" or "Update a Deal". Map only non-empty Clearbit values into the corresponding custom fields. Always preserve existing human-entered fields if Clearbit returns blanks.

  1. Append an audit row to Google Sheets

Add a Google Sheets "Add a Row" module to log each enrichment attempt with: person_id, email, company_domain, clearbit_status, lead_score, timestamp, and a short raw response or error note. This audit log helps troubleshoot mismatches and track API usage.

  1. Send a Slack alert for high-scoring leads

Add a Slack "Post a Message" step and filter to send only when lead_score crosses your threshold, for example 50. Use a tight message:

New enriched lead: Acme Co
Name: Jane Doe
Email: jane@acme.co
Company size: 500+
Industry: Fintech
Score: 70
Pipedrive: <https://app.pipedrive.com/person/{{person_id}}|Open contact>

Include the Pipedrive link for immediate action by the rep.

  1. Add error handling and a retry path

Configure Make.com to retry transient HTTP failures. For permanent failures update Pipedrive clearbit_enriched to failed and write the error into enrichment_notes. Provide a manual re-run option for records with status failed.

  1. Test with a representative set of records

Test across a mix of enterprise, small business, and personal email addresses. Verify domain parsing, Clearbit mappings, scoring, and Slack thresholds. Tune the score and mapping before enabling production alerts.

Real-World Business Scenario

A B2B software vendor used this workflow to enrich inbound demo requests. Before automation, SDRs manually checked LinkedIn and company sites to judge fit. After enrichment, each new person had company size, industry, and tech signals attached automatically. High-scoring leads triggered a Slack alert, enabling SDRs to prioritise outreach. The firm reduced time to meaningful outreach from hours to under 30 minutes for top prospects.

Common Variations

  • Enrich on form submission instead of Pipedrive, trigger from the form system and follow the same mapping. For a capture pattern to compare, see our Jotform to Pipedrive guide: Jotform to Pipedrive lead capture and deduplication.
  • Add enrichment caching by storing previously enriched domains in Google Sheets to reduce Clearbit calls and cost.
  • Chain additional enrichment vendors and compute a composite score from multiple sources.

How this helps your team

You now have a practical Make.com pattern to enrich Pipedrive leads with Clearbit, apply a simple score, keep an audit log, and notify sales for high-priority prospects. If you want this implemented, Olmec Dynamics builds these exact automations for businesses and can help tune scoring and field mappings. See what we do at https://olmecdynamics.com.