The flow
Starts it 2Logic 2Service 7
The steps in the order they run, from what starts it.
- 1On clicking 'execute'Manual triggerStarts it
- 2CronCronStarts it
- 3ConfigSetLogic
- 4Read Binary FileRead Binary FileService
- 5Binary to jsonMove Binary DataService
- 6HTTP RequestHttp RequestService
- 7Split into bachesFunctionLogic
- 8Set new update timeFunction ItemService
- 9TelegramTelegramService
- 10Json to binaryMove Binary DataService
- 11Write Binary FileWrite Binary FileService
How it's built
- Starts on
- A clock
- Steps
- 11
- 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. 11 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 11 steps before you point it at anything that matters.