The flow
Starts it 2Logic 9Service 7
The steps in the order they run, from what starts it.
- 1When clicking ‘Execute workflow’Manual triggerStarts it
- 2When Executed by Another WorkflowExecute Workflow triggerStarts it
- 3Get File from GitHubGithubService
- 4All PromptsSetLogic
- 5Image to Base64Extract From FileService
- 6Download Initial ImageHttp RequestService
- 7Number of StepsSetLogic
- 8FLUX KontextHttp RequestService
- 9MergeMergeLogic
- 10Wait 2 secWaitLogic
- 11IfIfLogic
- 12Check FLUX statusHttp RequestService
- 13Current StepSetLogic
- 14Upload PostUpload PostService
- 15Is Ready?IfLogic
- 16Run FLUXExecute WorkflowLogic
- 17Merge3MergeLogic
- 18Get ImageHttp RequestService
How it's built
- Starts on
- An event in a connected app
- Steps
- 18, with 2 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- GitHub
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own GitHub 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. 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.