The flow
Starts it 2Logic 9Service 5
The steps in the order they run, from what starts it.
- 1On clicking 'execute'Manual triggerStarts it
- 2Daily @ 20:00CronStarts it
- 3GlobalsSetLogic
- 4N8N WorkflowsHttp RequestService
- 5dataArrayFunctionLogic
- 6OneAtATimeSplit In BatchesLogic
- 7GitHubGithubService
- 8N8N Workflow DetailHttp RequestService
- 9MergeMergeLogic
- 10isDiffOrNewFunctionLogic
- 11github_statusSwitchLogic
- 12sameNo OpLogic
- 13differentNo OpLogic
- 14newNo OpLogic
- 15GitHub EditGithubService
- 16GitHub CreateGithubService
How it's built
- Starts on
- A clock
- Steps
- 16, with 1 branch, 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. 16 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 16 steps before you point it at anything that matters.