The flow
Starts it 1Logic 7Service 8
The steps in the order they run, from what starts it.
- 1Telegram Trigger – Receive FileTelegram triggerStarts it
- 2Validate File Type (Excel Only)CodeLogic
- 3If Not Excel → Send Error MessageIfLogic
- 4Download Excel from TelegramTelegramService
- 5Notify User – Processing StartedTelegramService
- 6Notify User – Invalid File FormatTelegramService
- 7Read Excel DataExtract From FileService
- 8Normalize Question DataCodeLogic
- 9Create Google FormHttp RequestService
- 10Enable Quiz ModeHttp RequestService
- 11Prepare Question PayloadSetLogic
- 12Loop Questions (Batch Processing)Split In BatchesLogic
- 13Add Question to FormHttp RequestService
- 14Rate Limit Delay (2.5s)WaitLogic
- 15Check All Questions ProcessedIfLogic
- 16Send Google Form Link to UserTelegramService
How it's built
- Starts on
- An incoming Telegram message
- Steps
- 16, with 2 branches, 2 loops or waits
- 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 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?
Plan an afternoon. 16 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 16 steps before you point it at anything that matters.