The flow
Starts it 1Logic 7Service 4
The steps in the order they run, from what starts it.
- 1On clicking 'execute'Manual triggerStarts it
- 2GlobalsSetLogic
- 3n8n - get all workflowsN8nService
- 4GitHub - get all filesGithubService
- 5Merge globals and filesMergeLogic
- 6Set n8n existing workflows namesSetLogic
- 7GitHub - get each fileGithubService
- 8Merge Github and n8n workflows - Keep only non existing workflows based on the nameMergeLogic
- 9Set name and contentSetLogic
- 10If workflow already existsIfLogic
- 11n8n - create workflowN8nService
- 12Workflow name already existsNo OpLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 12, with 1 branch
- 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 an event in a connected app.
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. 12 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 12 steps before you point it at anything that matters.