The flow
Starts it 1Model 2Logic 11Service 10
The steps in the order they run, from what starts it.
- 1When clicking ‘Execute workflow’Manual triggerStarts it
- 2Ideator 🧠Open AiModel
- 3ScriptSetLogic
- 4Script GeneratorHttp RequestService
- 5HTTP RequestHttp RequestService
- 6Upload CloudinaryHttp RequestService
- 7Split OutSplit OutLogic
- 8MergeMergeLogic
- 9image-prompterOpen AiModel
- 10Create editor JSONHttp RequestService
- 11request imageHttp RequestService
- 12SET JSON VARIABLESetLogic
- 13Wait2WaitLogic
- 14EditorHttp RequestService
- 15request image1Http RequestService
- 16Rendering waitWaitLogic
- 17Wait3WaitLogic
- 18Get final videoHttp RequestService
- 19request image2Http RequestService
- 20Wait4WaitLogic
- 21Request VideoHttp RequestService
- 22Wait1WaitLogic
- 23Edit FieldsSetLogic
- 24AggregateAggregateLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 24, 5 loops or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- OpenAI
Questions
What does it need to run?
An n8n account, and a key for OpenAI. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
Yes. It calls OpenAI. Model calls are billed by the provider, not by n8n.
How long does it take to set up?
Take your time. At 24 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 24 steps before you point it at anything that matters.