The flow
Starts it 1Logic 9Service 11
The steps in the order they run, from what starts it.
- 1Every Monday 07:00Schedule triggerStarts it
- 2Log error to SlackHttp RequestService
- 3ConfigSetLogic
- 4Umami, loginHttp RequestService
- 5Store tokenSetLogic
- 6Get client listHttp RequestService
- 7Flatten records + inject tokenCodeLogic
- 8Loop each clientSplit In BatchesLogic
- 9Has client?IfLogic
- 10Umami, this weekHttp RequestService
- 11Umami, prior weekHttp RequestService
- 12Umami, top pagesHttp RequestService
- 13Umami, traffic sourcesHttp RequestService
- 14Merge, all Umami dataMergeLogic
- 15Format data + build AI promptCodeLogic
- 16Groq, generate reportHttp RequestService
- 17Parse + format reportCodeLogic
- 18Send email reportEmail SendService
- 19Send Slack messageHttp RequestService
- 20Save history to AirtableHttp RequestService
- 21Wait (rate limit)WaitLogic
How it's built
- Starts on
- A clock
- Steps
- 21, with 1 branch, 2 loops or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- Email
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Email 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.