🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Pipedrive + Clearbit: enriched leads, Slack alerts

Pipedrive + Clearbit: enriched leads, Slack alerts - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Pipedrive + Clearbit: enriched leads, Slack alerts - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

New leads hit Pipedrive, and then… they sit. Or worse, they get “quickly reviewed” (skipped) because nobody has time to open every record, hunt for a domain, and guess if the company is even a fit.

This is where Pipedrive Slack alerts help a lot. Sales Ops feels the pain first, but a marketing manager routing MQLs and an agency owner managing multiple pipelines deal with the same mess. You want clean data and fast follow-up, without turning lead review into a daily chore.

This workflow enriches every new lead with Clearbit, marks it as processed, and only pings Slack when the lead matches your ideal criteria (like B2B + 100+ employees). You’ll see what it automates, what results to expect, and what you need to run it.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Pipedrive + Clearbit: enriched leads, Slack alerts

The Problem: New leads pile up without qualification

When every new lead looks the same in your CRM, you’re forced into manual triage. Someone checks the lead, clicks into the org, Googles the company, tries to find a domain, and then makes a judgment call with half the context. Do that 20 times a day and it quietly eats a couple hours. And because it’s repetitive, it’s inconsistent. One rep is strict, another is optimistic, and the follow-up timing depends on who happened to be online.

The friction compounds. Here’s where it breaks down in real teams.

  • Leads get contacted in the wrong order because nothing signals which ones are high intent or high value.
  • Your team spends time enriching records that were never a fit in the first place.
  • Missing or messy company data leads to awkward outreach and lower reply rates.
  • Without a clear “processed” marker, the same leads get reviewed twice (or not at all).

The Solution: Enrich every Pipedrive lead, then alert Slack only for the good ones

This n8n workflow runs on a simple schedule (every 5 minutes) and acts like a gatekeeper for your pipeline. It pulls in new leads from Pipedrive, grabs the related organization details, and uses Clearbit to enrich the company profile so you’re not guessing. After enrichment, it updates the lead to mark it as “enriched” using a custom date field, which prevents repeat processing. Then it applies your qualification rules (for example, “B2B” and “more than 100 employees”). Only the leads that pass get sent to Slack, which means your team gets fewer notifications, but the right ones.

The workflow starts with scheduled checks of Pipedrive leads. Clearbit fills in the missing business context, and n8n merges that data back into a single lead payload. Finally, Slack gets a message only when the lead matches your ideal customer profile.

What You Get: Automation vs. Results

Example: What This Looks Like

Say your team adds 20 new leads a day to Pipedrive. If manual review takes maybe 10 minutes per lead (open record, find domain, check size, decide), that’s about 3 hours a day. With this workflow, the “work” is basically waiting: it runs every 5 minutes, enriches in the background, and only posts the matches to Slack. You’ll still review the good ones, but you’re no longer spending hours to discover who to ignore.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Pipedrive to source leads and update custom fields.
  • Clearbit for company enrichment and firmographic data.
  • Slack to notify your team in real time.

Skill level: Intermediate. You’ll configure credentials and map two Pipedrive custom fields (Domain and Enriched at).

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A 5-minute scheduled run checks for new leads. n8n starts on a timer, then pulls recent leads from Pipedrive so nothing relies on someone remembering to “check later.”

Organization details get pulled in and cleaned up. The workflow fetches the org record for each lead, then sets a few key fields so Clearbit has what it needs (usually the domain or identifying info).

Clearbit enrichment adds the context you actually need. Firmographics like company type (B2B) and employee count come back, and n8n merges them into one usable lead object.

Pipedrive gets updated, then Slack only sees qualified leads. The workflow flags the lead with an “Enriched at” date, runs your filter (B2B + 100+ employees in the provided example), and posts a Slack message for each match.

You can easily modify the qualification rules to match your ICP, so the Slack channel reflects your current go-to-market focus. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Scheduled Trigger

Set the workflow to run automatically every few minutes to pull and enrich fresh leads.

  1. Add and open Scheduled 5-Minute Trigger.
  2. Set the schedule rule to run every minutes interval (this node is already configured for 5-minute intervals).
  3. Connect Scheduled 5-Minute Trigger to Configuration Mapper.

Step 2: Connect Pipedrive and Map Configuration Values

Define configuration values and pull leads from Pipedrive as the primary data source.

  1. Open Configuration Mapper and set the following values: slackChannel to #yourChannel, domainCustomFieldId to <Run "Show only custom organization fields" and copy the key>, and enrichedAtCustomFieldId to <Run "Show only custom lead fields" and copy the key>.
  2. Replace domainCustomFieldId2 and enrichedAtCustomFieldId2 in Configuration Mapper with your actual custom field IDs (currently [CONFIGURE_YOUR_API_KEY] placeholders).
  3. Open Retrieve All Leads and confirm Resource is lead and Operation is getAll.
  4. Credential Required: Connect your pipedriveApi credentials to Retrieve All Leads.

If you’re unsure about the custom field keys, run Utility: Retrieve Org Field Keys and Utility: Retrieve Lead Field Keys once to list available custom fields.

Step 3: Set Up Enrichment and Merge Logic

Fetch organization data, enrich the company profile, and merge it back into the lead record.

  1. Open Fetch Organization Details and set Organization ID to {{ $json.organization_id }}.
  2. Credential Required: Connect your pipedriveApi credentials to Fetch Organization Details.
  3. Open Enrich Company Profile and set Domain to {{ $json[$('Configuration Mapper').first().json.domainCustomFieldId2]}}.
  4. Credential Required: Connect your clearbitApi credentials to Enrich Company Profile.
  5. Open Append Org ID Field and add organization_id with value {{ $('Fetch Organization Details').item.json.id }}; keep Include Other Fields enabled.
  6. Open Combine Lead Details and set Mode to combine, Join Mode to enrichInput2, and merge by organization_id on both inputs.

⚠️ Common Pitfall: The merge depends on organization_id matching across inputs. Ensure Append Org ID Field runs after Fetch Organization Details and before Combine Lead Details.

Step 4: Configure Parallel Execution and Enrichment Updates

Ensure the lead retrieval fan-out is correctly wired and update the lead with the enriched timestamp.

  1. Connect Retrieve All Leads so it outputs to both Fetch Organization Details and Combine Lead Details in parallel.
  2. Open Flag Lead as Enriched and set URL to https://api.pipedrive.com/v1/leads/{{ $json.id }}, Method to PATCH, and enable Send Body.
  3. In Flag Lead as Enriched body parameters, set Name to {{ $('Configuration Mapper').first().json.enrichedAtCustomFieldId2 }} and Value to {{ $now.format('yyyy-MM-dd') }}.
  4. Credential Required: Connect your pipedriveApi credentials to Flag Lead as Enriched.

Step 5: Filter and Notify Qualified Leads

Apply qualification logic and send a Slack alert for high-quality leads.

  1. Open Filter Qualified Leads and confirm the conditions are: {{ $json.tags.includes("B2B") }} is true and {{ $json.metrics.employees }} is greater than 100.
  2. Open Post Slack Notification and set Text to New high-quality lead 🤑 *Company Name*: {{ $json.name }} *Website*: {{ "https://" + $json.domain }} *Revenue*: {{ $json.metrics.estimatedAnnualRevenue}} *Number of employees*: {{ $json.metrics.employees }}.
  3. Set Channel to {{ $('Configuration Mapper').item.json.slackChannel }}.
  4. Credential Required: Connect your slackApi credentials to Post Slack Notification.

If no Slack messages appear, inspect the output of Filter Qualified Leads to ensure your enrichment data contains tags and metrics.employees.

Step 6: (Optional) Retrieve and Filter Custom Field Keys

Use the utility nodes to discover custom field keys needed in Configuration Mapper.

  1. Open Utility: Retrieve Org Field Keys and confirm URL is https://api.pipedrive.com/v1/organizationFields.
  2. Credential Required: Connect your pipedriveApi credentials to Utility: Retrieve Org Field Keys and Utility: Retrieve Lead Field Keys.
  3. Open Utility: Expand Org Field Records and set Field to Split Out to data, then filter with Utility: Filter Custom Org Fields using {{ $json.edit_flag }}.
  4. Open Utility: Expand Lead Field Records and set Field to Split Out to data, then filter with Utility: Filter Custom Lead Fields using {{ $json.edit_flag }}.

Step 7: Test and Activate Your Workflow

Validate the full flow end-to-end before enabling scheduled runs.

  1. Click Execute Workflow to run a manual test.
  2. Confirm Retrieve All Leads outputs leads and Enrich Company Profile returns enrichment data.
  3. Verify Flag Lead as Enriched updates the lead with today’s date, and Post Slack Notification posts to your channel for qualified leads.
  4. Toggle the workflow to Active to enable the 5-minute schedule.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Pipedrive custom fields must be mapped correctly, or the Domain / Enriched at updates won’t stick. If results look wrong, check Company Settings → Data fields and confirm you copied the right field keys.
  • If you’re enriching lots of leads at once, Clearbit calls can take longer than expected. Processing times vary, so extend any wait/timeout handling if downstream steps fail on empty responses.
  • Slack alerts can become noisy if your filter is too broad. Honestly, tighten the criteria first, then loosen it once you trust the data quality.

Related Workflows

If your team also needs Slack alerts but your leads originate in HubSpot, HubSpot to Slack, never miss high value leads pairs nicely with this approach so every source gets the same “only notify on the good stuff” treatment.

For teams cleaning inbound lists before they even hit the CRM, Hunter + Pipedrive: clean leads, no duplicates is a smart add-on, because enrichment is more reliable when the base data isn’t messy.

When you like the “enrich + qualify” idea but want an alternative data provider, Pipedrive + Datagma: enriched leads, fewer bad fits is worth comparing for coverage in certain regions or industries.

Need the enrichment context to live inside Pipedrive instead of only in Slack? Pipedrive + Slack: enriched org notes for every lead focuses on pushing richer notes back to the record, which helps reps who live in the CRM.

Finally, if you want qualification to happen even earlier (before a lead ever becomes “sales-owned”), Hunter + Slack: only qualified leads hit your team is a good fit for outbound teams that start with email/domain discovery.


Quick reference:

Frequently Asked Questions

How long does it take to set up this Pipedrive Slack alerts automation?

About an hour if your Pipedrive custom fields are ready.

Do I need coding skills to automate Pipedrive lead enrichment?

No. You’ll connect Pipedrive, Clearbit, and Slack, then paste in the right field IDs. The only “technical” part is testing with a few sample leads to confirm the filter works.

Is n8n free to use for this Pipedrive Slack alerts workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Clearbit API costs (varies by plan and enrichment volume).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this Pipedrive Slack alerts workflow for different qualification rules?

Yes, and you should. Update the “Filter Qualified Leads” step to match your ICP, then adjust the Slack message to include the fields your reps actually scan (industry, employee count, location, and website are common). You can also change the schedule so it runs every few minutes during business hours and less often overnight. If you want to keep Pipedrive cleaner, a common tweak is archiving or labeling non-matches after enrichment so they stop distracting your team. Finally, you can swap Clearbit for another enrichment provider by replacing the “Enrich Company Profile” request and keeping the rest of the logic intact.

Why is my Pipedrive connection failing in this workflow?

Usually it’s expired credentials or missing permissions on the Pipedrive token. Reconnect the Pipedrive credential in n8n, then re-check that your custom field keys for Domain and Enriched at are correct, because wrong keys can look like “nothing happened.” If it fails only on some leads, it can also be missing organization links (a lead without an org won’t enrich the same way).

How many leads can this Pipedrive Slack alerts automation handle?

A lot, but the real limit is your Clearbit quota and how often you run the schedule.

Is this Pipedrive Slack alerts automation better than using Zapier or Make?

Often, yes, because the logic here is a bit more than “if new lead, then send message.” You’re enriching, merging org + lead data, writing back to Pipedrive, and filtering based on multiple fields. n8n handles branching and data shaping without pushing you into expensive task pricing, and self-hosting means you can run frequent checks without worrying about per-task costs. Zapier and Make can still work if you keep it very simple, but the “mark as enriched so it won’t re-run” pattern is where n8n tends to feel cleaner. Talk to an automation expert if you want help choosing based on your lead volume.

Once this is running, your team stops scanning every lead and starts responding to the ones that actually match. Set it up, tune the filter, and let Slack do the tapping on the shoulder.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.