The flow
Starts it 3Logic 12Service 8
The steps in the order they run, from what starts it.
- 1On clicking 'execute'Manual triggerStarts it
- 2Execute Workflow TriggerExecute Workflow triggerStarts it
- 3Schedule TriggerSchedule triggerStarts it
- 4Starting MessageSlackService
- 5ConfigSetLogic
- 6n8nN8nService
- 7Get file dataGithubService
- 8Merge ItemsMergeLogic
- 9Loop Over ItemsSplit In BatchesLogic
- 10If file too largeIfLogic
- 11isDiffOrNewCodeLogic
- 12Completed NotificationSlackService
- 13Execute WorkflowExecute WorkflowLogic
- 14Get FileHttp RequestService
- 15Create sub pathSetLogic
- 16Failed FlowsSlackService
- 17Check StatusSwitchLogic
- 18Same file - Do nothingNo OpLogic
- 19File is differentNo OpLogic
- 20File is newNo OpLogic
- 21ReturnSetLogic
- 22Edit existing fileGithubService
- 23Create new fileGithubService
How it's built
- Starts on
- A clock
- Steps
- 23, with 2 branches, 1 loop or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- GitHub, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own GitHub and Slack accounts. 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 23 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 23 steps before you point it at anything that matters.