The flow
Starts it 2Logic 4Service 10
The steps in the order they run, from what starts it.
- 1When Executed by Another WorkflowExecute Workflow triggerStarts it
- 2n8n TriggerN8n triggerStarts it
- 3Set publish variablesSetLogic
- 4Get n8n workflow JSONHttp RequestService
- 5Strip workflow metadataCodeLogic
- 6Get a repositoryGithubService
- 7Convert JSON to fileConvert To FileService
- 8Get main branch SHAHttp RequestService
- 9Create Github RepoHttp RequestService
- 10Extract JSON from fileExtract From FileService
- 11Create Github branchHttp RequestService
- 12Merge file dataMergeLogic
- 13Check Error MessageIfLogic
- 14Get existing file in repoHttp RequestService
- 15Add workflow to branchHttp RequestService
- 16Create Github Pull RequestHttp RequestService
How it's built
- Starts on
- An event in a connected app
- Steps
- 16, 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. 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.
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 16 steps before you point it at anything that matters.