Version control n8n workflows in GitLab with customer tag organization
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 17 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects GitLab.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Set Global GitLab Variables (Edit Fields (Set)): sets 6 fields: gitlab_owner, gitlab_project, gitlab_workflow_path…
- Fetch Workflows from n8n (n8n): uses n8n
- Clean & Normalize Workflow Name (Code): runs custom JavaScript code
- Prepare Workflow JSON for UI-Compatible Export (Code): runs custom JavaScript code
- Prepare GitLab File Path (Code): runs custom JavaScript code
- Fetch Existing File from GitLab (GitLab): get (file)
- Compare Workflow with GitLab Version (If): checks a condition and branches into true / false
- Create New File in GitLab (GitLab): work with file
- Update Existing File in GitLab (GitLab): edit (file)
- Mark as Unchanged (Edit Fields (Set)): sets 1 field: status
…plus 5 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Manual Trigger
n8n-nodes-base.manualTrigger - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Code
n8n-nodes-base.code - n8n
n8n-nodes-base.n8n - GitLab
n8n-nodes-base.gitlab - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Merge
n8n-nodes-base.merge
From the author
How it works - Triggers manually or on schedule (03:00 daily by default) - Fetches workflows tagged backup-workflows via n8n API - Normalizes workflow names and applies client: NAME tag convention - Prepares JSON in the same structure as an n8n UI export -…