The flow
Starts it 1Logic 9Service 12
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Set GitHub DetailsSetLogic
- 3n8nN8nService
- 4List files from repoGithubService
- 5n8n vs GitHubCompare DatasetsService
- 6FilterFilterLogic
- 7Json fileConvert To FileService
- 8If n8n before GitHubIfLogic
- 9Create new workflow in n8nN8nService
- 10GitHubGithubService
- 11To base64Extract From FileService
- 12Code - InputBCodeLogic
- 13Code - InputACodeLogic
- 14Decode to jsonSetLogic
- 15Edit for UploadSetLogic
- 16Update workflow in n8nN8nService
- 17Edit FieldsSetLogic
- 18Upload fileGithubService
- 19Json file1Convert To FileService
- 20To baseExtract From FileService
- 21Edit for UpdateSetLogic
- 22Update fileGithubService
How it's built
- Starts on
- A clock
- Steps
- 22, with 1 branch
- 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 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.
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 22 steps before you point it at anything that matters.