The flow
Starts it 2Logic 11Service 4
The steps in the order they run, from what starts it.
- 1When clicking ‘Execute workflow’Manual triggerStarts it
- 2Schedule TriggerSchedule triggerStarts it
- 3Set Global GitLab VariablesSetLogic
- 4Fetch Workflows from n8nN8nService
- 5Clean & Normalize Workflow NameCodeLogic
- 6Prepare Workflow JSON for UI-Compatible ExportCodeLogic
- 7Prepare GitLab File PathCodeLogic
- 8Fetch Existing File from GitLabGitlabService
- 9Compare Workflow with GitLab VersionIfLogic
- 10Create New File in GitLabGitlabService
- 11Update Existing File in GitLabGitlabService
- 12Mark as UnchangedSetLogic
- 13Mark as CreatedSetLogic
- 14Mark as UpdatedSetLogic
- 15MergeMergeLogic
- 16Normalize Backup OutputSetLogic
- 17Summarize Backup ResultsCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 17, with 1 branch
- 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. 17 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 17 steps before you point it at anything that matters.