Enrich new leads in Pipedrive and send an alert to Slack for high-quality ones
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 16 nodes and runs on a schedule (every minute). Along the way it connects Clearbit, Pipedrive and Slack. It also calls api.pipedrive.com over HTTP.
How it runs
Trigger: On a schedule (every minute).
- Setup (Edit Fields (Set)): sets 5 fields: slackChannel, domainCustomFieldId, enrichedAtCustomFieldId…
- Get all leads (Pipedrive): get many (lead)
- Get organization details (Pipedrive): get (organization)
- Merge: merges the data from its input branches
- Enrich company (Clearbit): uses Clearbit
- Mark lead as enriched in Pipedrive (HTTP Request): calls an HTTP API (PATCH)
- Add Organization ID to data (Edit Fields (Set)): sets 1 field: organization_id
- Keep leads that match the criteria (Filter): keeps only the items that match a condition
- Send alert to Slack (Slack): uses Slack
- Get all organization keys (HTTP Request): calls api.pipedrive.com
…plus 5 more steps. See the full node list below.
Services it uses
HTTP calls to: api.pipedrive.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Clearbit
n8n-nodes-base.clearbit - Pipedrive
n8n-nodes-base.pipedrive - Edit Fields (Set)
n8n-nodes-base.set - Filter
n8n-nodes-base.filter - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Slack
n8n-nodes-base.slack - Merge
n8n-nodes-base.merge - HTTP Request
n8n-nodes-base.httpRequest - Split Out
n8n-nodes-base.splitOut
From the author
Use Case This workflow is beneficial when you're automatically adding new leads to your Pipedrive CRM. Usually, you'd have to manually review each lead to determine if they're a good fit. This process is time-consuming and increases the chances of missing…