The flow
Starts it 2Logic 13Service 12
The steps in the order they run, from what starts it.
- 1Poll TriggerWebhookStarts it
- 2Parse InputCodeLogic
- 3Respond OKRespond To WebhookStarts it
- 4Wait 1 MinuteWaitLogic
- 5Check KIE StatusHttp RequestService
- 6Parse StatusCodeLogic
- 7Completed?IfLogic
- 8Get 1080p VideoCodeLogic
- 9Can Retry?IfLogic
- 10Get Final URLCodeLogic
- 11Retry PollHttp RequestService
- 12Send TimeoutTelegramService
- 13Download VideoHttp RequestService
- 14Upload a fileS3Service
- 15Is Extend?IfLogic
- 16Send Merge OptionsTelegramService
- 17Skip ConcatCodeLogic
- 18Merge After ConcatMergeLogic
- 19Get SessionRedisService
- 20Merge Session DataCodeLogic
- 21Create MetadataCodeLogic
- 22Upload MetadataS3Service
- 23Update SessionRedisService
- 24Download for TelegramS3Service
- 25Is Veo Model?IfLogic
- 26Send Video Preview (Veo)TelegramService
- 27Send Video Preview (Other)TelegramService
How it's built
- Starts on
- Another system calling it
- Steps
- 27, with 4 branches, 1 loop or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- Redis, S3, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Redis, S3 and Telegram accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling it.
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 27 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 27 steps before you point it at anything that matters.