The flow
Starts it 1Logic 8Service 9
The steps in the order they run, from what starts it.
- 1get httpWebhookStarts it
- 2get_appHttp RequestService
- 3get_photoHttp RequestService
- 4Clear_photo_structureCodeLogic
- 5Split OutSplit OutLogic
- 6Loop Over ItemsSplit In BatchesLogic
- 7devide_two_photoCodeLogic
- 8download_photo_privatelyHttp RequestService
- 9post_public_linkHttp RequestService
- 10AggregateAggregateLogic
- 11gen_ai_pictureHttp RequestService
- 12Wait 15 secWaitLogic
- 13get_ai_pictureHttp RequestService
- 14situationsSwitchLogic
- 15get_urlSetLogic
- 16download_generated_photoHttp RequestService
- 17Upload to betabaseHttp RequestService
- 18update_rowHttp RequestService
How it's built
- Starts on
- Another system calling it
- Steps
- 18, with 1 branch, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. 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?
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.