The flow
Starts it 3Logic 11Service 5
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
- 4n8nN8nService
- 5GlobalsSetLogic
- 6Merge ItemsMergeLogic
- 7Loop Over ItemsSplit In BatchesLogic
- 8Get file dataGithubService
- 9isDiffOrNewCodeLogic
- 10Execute WorkflowExecute WorkflowLogic
- 11If file too largeIfLogic
- 12Check StatusSwitchLogic
- 13Get FileHttp RequestService
- 14Same file - Do nothingNo OpLogic
- 15File is differentNo OpLogic
- 16File is newNo OpLogic
- 17ReturnSetLogic
- 18Edit existing fileGithubService
- 19Create new fileGithubService
How it's built
- Starts on
- A clock
- Steps
- 19, 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 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?
Plan an afternoon. 19 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 19 steps before you point it at anything that matters.