Templates / Backup tag-selected workflows to Gitlab

Backup tag-selected workflows to Gitlab

Ready for 3.0

by Hubschrauber ✓ · 2,033 views · created 2024-08-11 · DevOps

Ready 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 12 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).

  1. Globals (Edit Fields (Set)): sets 6 fields: gitlab_owner, gitlab_project, gitlab_workflow_path…
  2. Fetch List of Existing Files (GitLab): list (file)
  3. Combine Gitlab Existing Files as Single List Item (Aggregate): combines items into one
  4. n8n: uses n8n
  5. Derive Filename From Workflow Name (Edit Fields (Set)): sets 1 field: normalized_filename
  6. File Exists in Gitlab? (If): checks a condition and branches into true / false
  7. Fetch Existing File Content (GitLab): get (file)
  8. Create New File(s) (GitLab): work with file
  9. Skip Unchanged Files (Filter): keeps only the items that match a condition
  10. Edit Existing File(s) (GitLab): edit (file)

Services it uses

GitLab

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)

From the author

Fetches workflow definitions from within n8n, selecting only the ones that have one or more (configurable) assigned tags and then: 1. Derives a suitable backup filename by reducing the workflow name to a string with alphanumeric characters and no-spaces Note:…

Excerpt from Hubschrauber's description on n8n.io.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.