The flow
Starts it 1Logic 4Service 7
The steps in the order they run, from what starts it.
- 1When Scheduled At 10amSchedule triggerStarts it
- 2Read Config File from DiskRead Write FileService
- 3Extract Config DataExtract From FileService
- 4Split Data by FieldSplit OutLogic
- 5Loop Over Split ItemsSplit In BatchesLogic
- 6Set Additional MetricsSetLogic
- 7Fetch Marketplace StatsHttp RequestService
- 8Convert Data to FileConvert To FileService
- 9Set Marketplace MetricsSetLogic
- 10Post Slack AlertSlackService
- 11Send Outlook NotificationMicrosoft OutlookService
- 12Save Data to DiskRead Write FileService
How it's built
- Starts on
- A clock
- Steps
- 12, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Outlook, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Outlook 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. 12 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 12 steps before you point it at anything that matters.