The flow
Starts it 1Logic 6Service 9
The steps in the order they run, from what starts it.
- 1When clicking ‘Execute workflow’Manual triggerStarts it
- 2Run a workflowBrowser ActService
- 3Parse BrowserAct outputCodeLogic
- 4limit_productsLimitLogic
- 5iterate_productsSplit In BatchesLogic
- 6fetch_imageHttp RequestService
- 7Convert image to Base64Extract From FileService
- 8Prepare image for video generationConvert To FileService
- 9upload_source_imageGoogle DriveService
- 10set_promptSetLogic
- 11Submit video generation requestHttp RequestService
- 12Wait for video generationWaitLogic
- 13Check video generation statusHttp RequestService
- 14check_responseIfLogic
- 15download_videoHttp RequestService
- 16upload_output_videoGoogle DriveService
How it's built
- Starts on
- An event in a connected app
- Steps
- 16, with 1 branch, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- Google Drive
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Drive account. 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?
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.
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 16 steps before you point it at anything that matters.