The flow
Starts it 1Logic 12Service 6
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2GitLabGitlabService
- 3GlobalsSetLogic
- 4Retrieve all workflowsN8nService
- 5Loop Over WorkflowsSplit In BatchesLogic
- 6ResultNo OpLogic
- 7Current workflowNo OpLogic
- 8Get fileGitlabService
- 9Extract From FileExtract From FileService
- 10Error output to normal outputNo OpLogic
- 11Save each version in a different fieldSetLogic
- 12File statusCodeLogic
- 13SwitchSwitchLogic
- 14Create fileGitlabService
- 15Status sameSetLogic
- 16New file versionGitlabService
- 17Status errorSetLogic
- 18End LoopNo OpLogic
- 19Status diffSetLogic
How it's built
- Starts on
- A clock
- Steps
- 19, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- GitLab
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own GitLab 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. 19 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 19 steps before you point it at anything that matters.