The flow
Starts it 1Logic 21Service 7
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Define WeeksCodeLogic
- 3IfIfLogic
- 4priorWeekHttp RequestService
- 5lastWeekHttp RequestService
- 6labelCodeLogic
- 7label1CodeLogic
- 8FlattenCodeLogic
- 9Flatten1CodeLogic
- 10MergeMergeLogic
- 11Merge WeeksCodeLogic
- 12Tag Brand / Recipes / NonbrandCodeLogic
- 13Aggregate by KWCodeLogic
- 14SwitchSwitchLogic
- 15Top Movers FilterCodeLogic
- 16Top 25 FilterCodeLogic
- 17Top 25 Filter1CodeLogic
- 18Top Movers Filter1CodeLogic
- 19Top 25 Filter2CodeLogic
- 20Top Movers Filter2CodeLogic
- 21Top 25 Filter3CodeLogic
- 22Top Movers Filter3CodeLogic
- 23Top WoW Movers AlertSlackService
- 24Merge4MergeLogic
- 25Top WoW Movers Alert1SlackService
- 26Top WoW Movers Alert2SlackService
- 27Top WoW Movers Alert3SlackService
- 28CodeCodeLogic
- 29Top WoW Movers EmailGmailService
How it's built
- Starts on
- A clock
- Steps
- 29, with 2 branches
- Size
- Large: read it before trusting it with anything live
- Connects to
- Gmail, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail 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?
Take your time. At 29 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 29 steps before you point it at anything that matters.