The flow
Starts it 1Logic 10Service 6
The steps in the order they run, from what starts it.
- 1Run Weekly on Sunday 6amSchedule triggerStarts it
- 2Channel SummaryHttp RequestService
- 3Top Videos WeekHttp RequestService
- 4Traffic SourceHttp RequestService
- 5Audience DemographicsHttp RequestService
- 6Channel Summary FormatterCodeLogic
- 7Top Videos Week FormatterCodeLogic
- 8Traffic Source FormatterCodeLogic
- 9Audience Demographics FormatterCodeLogic
- 10Merger Node 1 2MergeLogic
- 11Turn Id to TitleHttp RequestService
- 12Merger Views Weekly and Views All TimeMergeLogic
- 13Merger Node 1 2 3MergeLogic
- 14Merger Node 1 2 3 4MergeLogic
- 15All Output FormatterCodeLogic
- 16Telegram Message FormatterCodeLogic
- 17Send a text messageTelegramService
How it's built
- Starts on
- A clock
- Steps
- 17
- Size
- Medium: a working afternoon
- Connects to
- Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Telegram 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?
Plan an afternoon. 17 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 17 steps before you point it at anything that matters.