The flow
Starts it 1Logic 11Service 6
The steps in the order they run, from what starts it.
- 1When Monday at 8amSchedule triggerStarts it
- 2Set Search ParametersSetLogic
- 3Search Jobs via CoresignalCoresignalService
- 4Extract Job IDsCodeLogic
- 5Loop Over Job BatchesSplit In BatchesLogic
- 6Create Slack DigestCodeLogic
- 7Collect Job DetailsCoresignalService
- 8Send Digest to SlackSlackService
- 9Prepare Job RecordCodeLogic
- 10Check Company DomainIfLogic
- 11Enrich Company DetailsCoresignalService
- 12Handle Missing HR InfoCodeLogic
- 13Check Company MatchIfLogic
- 14Search HR ContactsCoresignalService
- 15Select Top HR IDCodeLogic
- 16Check HR ProfileIfLogic
- 17Collect HR DetailsCoresignalService
- 18Merge Job and HR DataCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 18, with 3 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack account. 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. 18 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 18 steps before you point it at anything that matters.