The flow
Starts it 4Logic 12Service 9
The steps in the order they run, from what starts it.
- 11st of Month 6PMSchedule triggerStarts it
- 2Every Friday 6PMSchedule triggerStarts it
- 3Milestone (daily check 9AM)Schedule triggerStarts it
- 4Telegram TriggerTelegram triggerStarts it
- 5Fetch Monthly DigestCodeLogic
- 6Fetch Weekly DigestCodeLogic
- 7Check MilestonesCodeLogic
- 8Parse CommandCodeLogic
- 9Send Monthly DigestTelegramService
- 10Send Weekly DigestTelegramService
- 11Has Milestones?IfLogic
- 12Switch CommandSwitchLogic
- 13Send Milestone AlertTelegramService
- 14Fetch All-Time DownloadsCodeLogic
- 15Fetch Weekly DownloadsCodeLogic
- 16Fetch StatusCodeLogic
- 17Fetch TrendingCodeLogic
- 18Help MessageCodeLogic
- 19Unknown CommandCodeLogic
- 20Send DownloadsTelegramService
- 21Send WeeklyTelegramService
- 22Send StatusTelegramService
- 23Send TrendingTelegramService
- 24Send HelpTelegramService
- 25Send UnknownTelegramService
How it's built
- Starts on
- An incoming Telegram message
- Steps
- 25, with 2 branches
- Size
- Large: read it before trusting it with anything live
- 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 an incoming Telegram message.
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 25 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 25 steps before you point it at anything that matters.