The flow
Starts it 1Logic 6Service 7
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2List Files in GitHub RepoGithubService
- 3Collect GitHub FilenamesAggregateLogic
- 4Fetch All n8n WorkflowsN8nService
- 5Filter Changed/New WorkflowsCodeLogic
- 6Convert Workflow to JSON FileConvert To FileService
- 7Encode as Base64Extract From FileService
- 8Build Filename & Commit DateSetLogic
- 9File Already Exists in Repo?IfLogic
- 10Update Existing FileGithubService
- 11Create New FileGithubService
- 12Find Orphaned Files to DeleteCodeLogic
- 13Any Files to Delete?IfLogic
- 14Delete Orphaned FileGithubService
How it's built
- Starts on
- A clock
- Steps
- 14, with 2 branches
- 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. 14 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.
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 14 steps before you point it at anything that matters.