The flow
Starts it 1Logic 11Service 4
The steps in the order they run, from what starts it.
- 1When clicking 'Execute workflow'Manual triggerStarts it
- 2Configure InputsSetLogic
- 3Build Inputs ArrayCodeLogic
- 4Submit Mobile Finder JobHttp RequestService
- 5Store Run IDSetLogic
- 6Wait 30 Seconds Before First PollWaitLogic
- 7Poll Loop ControllerSplit In BatchesLogic
- 8Check Job StatusHttp RequestService
- 9Is Job Complete?IfLogic
- 10Download Mobile Finder ResultsHttp RequestService
- 11Wait 60 Seconds Before RetryWaitLogic
- 12Parse CSV ResultsCodeLogic
- 13Remove Duplicate ContactsRemove DuplicatesLogic
- 14Filter Records With Phone NumbersFilterLogic
- 15Format Slack MessageCodeLogic
- 16Alert Sales Team in SlackSlackService
How it's built
- Starts on
- An event in a connected app
- Steps
- 16, with 1 branch, 3 loops 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 an event in a connected app.
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.