The flow
Starts it 3Logic 17Service 7
The steps in the order they run, from what starts it.
- 1On clicking 'execute'Manual triggerStarts it
- 2Schedule TriggerSchedule triggerStarts it
- 3Execute Workflow TriggerExecute Workflow triggerStarts it
- 4GlobalsSetLogic
- 5SwitchSwitchLogic
- 6Get many workflowsN8nService
- 7Get file dataGithubService
- 8MergeMergeLogic
- 9isDeletedCodeLogic
- 10WorkflowsAggregateLogic
- 11n8nSetLogic
- 12If file too largeIfLogic
- 13isDiffOrNewCodeLogic
- 14IfIfLogic
- 15List filesGithubService
- 16Loop Over ItemsSplit In BatchesLogic
- 17Get FileHttp RequestService
- 18Check StatusSwitchLogic
- 19Delete a fileGithubService
- 20ReturnSetLogic
- 21githubSetLogic
- 22Execute WorkflowExecute WorkflowLogic
- 23File is newNo OpLogic
- 24File is differentNo OpLogic
- 25Same file - Do nothingNo OpLogic
- 26Create new fileGithubService
- 27Edit existing fileGithubService
How it's built
- Starts on
- A clock
- Steps
- 27, with 4 branches, 1 loop or waits
- 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 a clock.
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 27 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.
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 27 steps before you point it at anything that matters.