The flow
Starts it 1Logic 14Service 6
The steps in the order they run, from what starts it.
- 1Schedule Trigger1Schedule triggerStarts it
- 2Define DaysCodeLogic
- 3IfIfLogic
- 4priorDayHttp RequestService
- 5lastDayHttp RequestService
- 6labelCodeLogic
- 7label1CodeLogic
- 8FlattenCodeLogic
- 9Flatten1CodeLogic
- 10MergeMergeLogic
- 11Merge DaysCodeLogic
- 12Tag KWs by CategoryCodeLogic
- 13Segment SwitchSwitchLogic
- 14Top Movers FilterCodeLogic
- 15Top Movers Filter1CodeLogic
- 16Top Movers Filter2CodeLogic
- 17Top Movers Filter3CodeLogic
- 18Top DoD Movers AlertSlackService
- 19Top DoD Movers Alert1SlackService
- 20Top DoD Movers Alert2SlackService
- 21Top DoD Movers Alert3SlackService
How it's built
- Starts on
- A clock
- Steps
- 21, with 2 branches
- Size
- Large: read it before trusting it with anything live
- 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?
Take your time. At 21 steps it is large: read it before trusting it with anything live.
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 21 steps before you point it at anything that matters.