The flow
Starts it 2Logic 12Service 8
The steps in the order they run, from what starts it.
- 1DevOps FormForm triggerStarts it
- 2Workflow Error TriggerError triggerStarts it
- 3Fetch Local WorkflowN8nService
- 4Build Error ResponseSetLogic
- 5Repo ConfigSetLogic
- 6Build File ContextCodeLogic
- 7Get GitHub File SHAHttp RequestService
- 8Code in JavaScriptCodeLogic
- 9Content Changed?IfLogic
- 10GitHub File Exists?IfLogic
- 11No Changes DetectedSetLogic
- 12Update GitHub FileGithubService
- 13Create GitHub FileGithubService
- 14Is Production Deploy?IfLogic
- 15Find Workflow on ProdN8nService
- 16Sandbox Backup CompleteSetLogic
- 17Resolve Prod Workflow IDCodeLogic
- 18Workflow Exists on Prod?IfLogic
- 19Update on Prod ServerN8nService
- 20Create on Prod ServerN8nService
- 21Activate on ProductionN8nService
- 22Build Success ResponseSetLogic
How it's built
- Starts on
- Someone submitting a form
- Steps
- 22, with 4 branches
- Size
- Large: read it before trusting it with anything live
- 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 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?
Take your time. At 22 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.
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 22 steps before you point it at anything that matters.