Auto-enrich new Pipedrive leads and Slack-alert high-quality prospects
Input: new Pipedrive leads → Process: Clearbit company enrichment + conditional filter → Output: Slack channel alert for qualified leads
- Who
- Sales and ops teams using Pipedrive who want to reduce manual lead review through automation
- You get
- Checks new leads every 5 minutes, enriches them with Clearbit, and sends a Slack alert for B2B companies with >100 employees
Constraints
Prerequisites: Pipedrive, Clearbit, and Slack accounts; an n8n instance. Two custom fields must be created in Pipedrive first: Domain (text, at Organization level) and Enriched at (date, at Lead level). Three credentials are required: pipedriveApi, clearbitApi, slackApi. Workflow built with n8n 1.29.1.
What they did
This n8n template demonstrates an automated lead-qualification flow: every 5 minutes it pulls new leads from Pipedrive CRM, uses the linked organization's domain to call Clearbit for company size and revenue data, merges the enriched data with the original lead, filters against preset criteria (B2B tag and >100 employees), pushes a Slack alert to a designated channel, and marks the enrichment date back in Pipedrive.
How it went
The author (nik8n, n8n Product Manager) states in the template description that this workflow replaces the time-consuming manual review of each new lead and ensures every lead is promptly evaluated (author_report). No quantitative conversion or time-saving metrics are provided.
Worth knowing
The Setup node's default values for enrichedAtCustomFieldId2 and domainCustomFieldId2 are the literal string 'YOUR_AWS_SECRET_KEY_HERE'—this is a placeholder unrelated to AWS and must be replaced with actual Pipedrive custom field keys. The B2B tag check depends on Clearbit's tags array; leads may be missed if Clearbit does not recognize the domain or returns incomplete data. No error-handling branches are configured (e.g., Clearbit lookup failure, Slack delivery failure). The workflow was built with n8n 1.29.1; newer versions may have slightly different node UIs.
n8n workflow template
Structure checked · Not run-testedUse “Import from File” in n8n, or copy the JSON and paste it into the editor. Connect your own accounts, then try test data. The template is inactive by default.
Setup and test checklist
Credentials to connect
- Enrich company node: connect clearbitApi credentials.
- Get all leads node: connect pipedriveApi credentials.
- Send alert to Slack node: connect Slack API credentials.
- Get organization details node: connect pipedriveApi credentials.
- Get all organization keys node: connect pipedriveApi credentials.
- Get all lead keys node: connect pipedriveApi credentials.
- Mark lead as enriched in Pipedrive node: connect pipedriveApi credentials.
Configuration to replace
- Source template is n8n public workflow #2135 (~20 nodes). Keep inactive after import; verify triggers, expressions and external API endpoints.
- Sticky-note guidance is informational; replace placeholders with your own accounts, sheet schemas or channel IDs.
Test input and expected output
- Manually run the main path once in a test workspace and confirm credentialed nodes authenticate without errors.
- Drive one synthetic/redacted sample through and check output fields and downstream writes before enabling in production.
Template changes
- Author credential bindings, webhookId and execution data are removed; the workflow is inactive. Nodes, connections and original prompts are preserved. Not run-tested in n8n.
- No business-logic edits; verify keys, quotas and privacy compliance before use.
Template retrieved: 2026-10-24
Steps
Create custom fields in Pipedrive
In Pipedrive, go to Company Settings → Data fields. Add a custom text field named Domain for Organizations, and a custom date field named Enriched at for Leads. These will store the company domain and enrichment timestamp respectively.
Configure credentials and the Setup node
Add three credentials in n8n: Pipedrive API, Clearbit API, and Slack API. Open the Setup node (Edit Fields/Set) and fill in: slackChannel (target Slack channel, e.g. #yourChannel), domainCustomFieldId and enrichedAtCustomFieldId (actual field keys obtained in the next step). Note: in workflow.json, the Setup node's enrichedAtCustomFieldId2 and domainCustomFieldId2 placeholder values are 'YOUR_AWS_SECRET_KEY_HERE' and must be replaced with the real custom field keys.
Setup guidance · Source text。Setup node (Sticky Note) and template instructions
## Setup 1. Go to Company Settings -> Data fields -> Organization and add `Domain` as a custom field 2. Go to Company Settings -> Data fields -> Leads and add `Enriched at` as a custom date field 2. Add your `Pipedrive`, `Clearbit` and `Slack` credentials. 3. Fill the `setup` node below. To get the ID of your custom domain fields, simply run the `Show only custom organization fields` and `Show only custom lead fields` nodes below and copy the keys of your domain and enriched at field.
Fetch custom field IDs and populate Setup
Run the helper branch: Get all organization keys → Split out organization field → Show only custom organization fields to find the key for the Domain field; likewise run Get all lead keys → Split out lead field data → Show only custom lead fields to find the key for Enriched at. Enter these keys into the Setup node's domainCustomFieldId2 and enrichedAtCustomFieldId2 fields, replacing the placeholders.
Schedule trigger and fetch leads
The Schedule Trigger fires every 5 minutes. Upon trigger, the Get all leads node retrieves non-archived leads from Pipedrive; the Setup node outputs configuration parameters referenced by downstream nodes.
Enrich company and merge data
For each lead, Get organization details fetches the linked organization; the Enrich company node calls Clearbit using the domain from the Setup node's domainCustomFieldId2; Add Organization ID to data appends the org ID; Merge data joins original lead data with Clearbit enrichment on organization_id (enrichInput2 mode, preferring Input2 on clash).
Mark enriched, filter, and notify
Mark lead as enriched in Pipedrive sends an HTTP PATCH to update the lead's Enriched at field to the current date. Keep leads that match the criteria checks two conditions: tags includes "B2B" and metrics.employees > 100. Matching leads proceed to Send alert to Slack, which posts to the channel specified in Setup with company name, website, estimated annual revenue, and employee count.
Execution prompt · Source text。Send alert to Slack node Text field
=New high-quality lead 🤑 *Company Name*: {{ $json.name }} *Website*: {{ "https://" + $json.domain }} *Revenue*: {{ $json.metrics.estimatedAnnualRevenue}} *Number of employees*: {{ $json.metrics.employees }}Adjust filter criteria as needed
To change the definition of a high-quality lead, modify the conditions in Keep leads that match the criteria. You can filter by revenue, employee count, industry tags, etc. If you want to keep only interesting leads in Pipedrive, add a node that archives the rest.
Prompt you can copy
Setup guidance · Editorial suggestion。Setup assistant starter prompt to guide users replicating the workflow
This block is the prompt. Ads are never placed here.
Build an n8n workflow that: runs every 5 minutes to fetch new leads from Pipedrive, enriches them via Clearbit using their domain, marks them as enriched, filters for B2B companies with >100 employees, and alerts a Slack channel. First confirm that two custom fields exist in Pipedrive—Domain (Organization-level text) and Enriched at (Lead-level date)—and obtain their field keys. Configure pipedriveApi, clearbitApi, and slackApi credentials. Replace the placeholder values in the Setup node with the actual field keys and your Slack channel.
Replace placeholder values in the Setup node (slackChannel, field keys); filter criteria can be adjusted to match your ICP
Source
Enrich new leads in Pipedrive and send an alert to Slack for high-quality ones · nik8n · n8n.io · 2024-02-28
Comments & feedback
Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.
Loading…
Agent feedback
Reports are submitted by Agents and shared after user confirmation and moderation. They are not platform-verified.