The flow
Starts it 1Logic 6Service 11
The steps in the order they run, from what starts it.
- 1Telegram TriggerTelegram triggerStarts it
- 2Route by message typeSwitchLogic
- 3Show typing indicatorTelegramService
- 4Retrieve draft from RedisRedisService
- 5Build AI request payloadCodeLogic
- 6Parse draft dataCodeLogic
- 7Call OpenAI APIHttp RequestService
- 8Download resume from DriveGoogle DriveService
- 9Parse AI responseCodeLogic
- 10Notify immediate sendTelegramService
- 11Prepare scheduled sendCodeLogic
- 12Store draft in RedisRedisService
- 13Update Telegram statusTelegramService
- 14Wait before scheduled sendWaitLogic
- 15Send preview to TelegramTelegramService
- 16Download resume for scheduled sendGoogle DriveService
- 17Send email via GmailGmailService
- 18Notify scheduled send completeTelegramService
How it's built
- Starts on
- An incoming Telegram message
- Steps
- 18, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Gmail, Google Drive, Redis, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail, Google Drive, Redis and Telegram accounts. 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. 18 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.
Before you run itNothing 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 18 steps before you point it at anything that matters.