The flow
Starts it 1Logic 9Service 11
The steps in the order they run, from what starts it.
- 1Telegram TriggerTelegram triggerStarts it
- 2SwitchSwitchLogic
- 3Merge1MergeLogic
- 4msg_pleasewaitTelegramService
- 5Merge2MergeLogic
- 6MergeMergeLogic
- 7msg_greetTelegramService
- 8FilenameSetLogic
- 9msg_wrongcommandTelegramService
- 10City ListFunctionLogic
- 11Get weather dataHttp RequestService
- 12Any errors API?IfLogic
- 13msg_errorAPITelegramService
- 14Convert API responseFunctionLogic
- 15Spreadsheet FileSpreadsheet FileService
- 16Write csvWrite Binary FileService
- 17Run R scriptExecute CommandService
- 18R successful?IfLogic
- 19Read Binary FileRead Binary FileService
- 20msg_errorRTelegramService
- 21msg_getweatherTelegramService
How it's built
- Starts on
- An incoming Telegram message
- Steps
- 21, with 3 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 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.