The flow
Starts it 2Logic 8Service 8
The steps in the order they run, from what starts it.
- 1Telegram TriggerTelegram triggerStarts it
- 2When clicking ‘Execute workflow’Manual triggerStarts it
- 3SanitazeCodeLogic
- 4Fix Image UrlSetLogic
- 5SwitchSwitchLogic
- 6Get ImageTelegramService
- 7Set FTP paramsSetLogic
- 8MergeMergeLogic
- 9Upload to FTPFtpService
- 10FTP Image URLSetLogic
- 11Create ImageHttp RequestService
- 12Wait 60 sec.WaitLogic
- 13Get statusHttp RequestService
- 14Completed?IfLogic
- 15Get Url imageHttp RequestService
- 16Get File imageHttp RequestService
- 17Upload ImageGoogle DriveService
- 18Upload to FTP1FtpService
How it's built
- Starts on
- An incoming Telegram message
- Steps
- 18, with 2 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- FTP, Google Drive, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own FTP, Google Drive 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.
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 18 steps before you point it at anything that matters.