The flow
Starts it 1Logic 13Service 5
The steps in the order they run, from what starts it.
- 1When clicking "Test Workflow"Manual triggerStarts it
- 2GlobalsSetLogic
- 3Retrieve all workflowsN8nService
- 4Loop Over WorkflowsSplit In BatchesLogic
- 5ResultNo OpLogic
- 6Current workflowNo OpLogic
- 7Get fileGitlabService
- 8Extract From FileExtract From FileService
- 9Error output to normal outputNo OpLogic
- 10Save each version in a different fieldSetLogic
- 11File statusCodeLogic
- 12SwitchSwitchLogic
- 13Create fileGitlabService
- 14Status sameSetLogic
- 15New file versionGitlabService
- 16Status errorSetLogic
- 17Status newSetLogic
- 18End LoopNo OpLogic
- 19Status diffSetLogic
How it's built
- Starts on
- An event in a connected app
- 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 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. 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.