The flow
Starts it 1Logic 8Service 7
The steps in the order they run, from what starts it.
- 1Trigger every 5 minutesSchedule triggerStarts it
- 2Get all organization keysHttp RequestService
- 3Get all lead keysHttp RequestService
- 4SetupSetLogic
- 5Split out organization fieldSplit OutLogic
- 6Split out lead field dataSplit OutLogic
- 7Get all leadsPipedriveService
- 8Show only custom organization fieldsFilterLogic
- 9Show only custom lead fieldsFilterLogic
- 10Get organization detailsPipedriveService
- 11Merge dataMergeLogic
- 12Enrich companyClearbitService
- 13Mark lead as enriched in PipedriveHttp RequestService
- 14Add Organization ID to dataSetLogic
- 15Keep leads that match the criteriaFilterLogic
- 16Send alert to SlackSlackService
How it's built
- Starts on
- A clock
- Steps
- 16
- Size
- Medium: a working afternoon
- Connects to
- Pipedrive, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Pipedrive and Slack accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 16 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 16 steps before you point it at anything that matters.