The flow
Starts it 2Logic 5Service 5
The steps in the order they run, from what starts it.
- 1Backup Now - Manual TriggerManual triggerStarts it
- 2Schedule TriggerSchedule triggerStarts it
- 3GlobalsSetLogic
- 4Fetch List of Existing FilesGitlabService
- 5Combine Gitlab Existing Files as Single List ItemAggregateLogic
- 6n8nN8nService
- 7Derive Filename From Workflow NameSetLogic
- 8File Exists in Gitlab?IfLogic
- 9Fetch Existing File ContentGitlabService
- 10Create New File(s)GitlabService
- 11Skip Unchanged FilesFilterLogic
- 12Edit Existing File(s)GitlabService
How it's built
- Starts on
- A clock
- Steps
- 12, 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. 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.