The flow
Starts it 2Logic 12Service 6
The steps in the order they run, from what starts it.
- 1On form submissionForm triggerStarts it
- 2StartExecute Workflow triggerStarts it
- 3Parse inputs given from formCodeLogic
- 4POST request to Replicate APIHttp RequestService
- 5MergeMergeLogic
- 6Call 'POST + GET requests sub-workflow'Execute WorkflowLogic
- 7Wait1WaitLogic
- 8Code in JavaScriptCodeLogic
- 9Isolate 1 process idCodeLogic
- 10GET Request for Riverflow PredictionsHttp RequestService
- 11Insert rowData TableService
- 12Insert empty process idData TableService
- 13Check if output is presentIfLogic
- 14Isolate 1 process id1CodeLogic
- 15Return output image urlSetLogic
- 16WaitWaitLogic
- 17Get how many processes doneData TableService
- 18If number of processes is correctIfLogic
- 19Output FilteringCodeLogic
- 20Get image/sHttp RequestService
How it's built
- Starts on
- Someone submitting a form
- Steps
- 20, with 2 branches, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- n8n data table
- 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 someone submitting a form.
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. 20 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 20 steps before you point it at anything that matters.