Most-used GitLab workflows
- Automated Kubernetes Testing with Robot Framework, Argocd & with Kind Lifecycle (73 nodes)
- Version Control N8n Workflows in Gitlab with Customer Tag Organization — n8n GitLab workflow (24 nodes)
- Daily Workflow Backup to Gitlab with Slack Notifications (22 nodes)
- Gitlab Code — n8n GitLab workflow (21 nodes)
- Save Your Workflows Into a Gitlab Repository (21 nodes)
- V3.7 — n8n GitLab workflow (19 nodes)
- Gitlabbackup (19 nodes)
- Automated Daily Backup of N8n Workflows to Gitlab Repositories — n8n GitLab workflow (19 nodes)
- Track Certification Requirements with Scrapegraphai, Gitlab and Rocket.chat (18 nodes)
- Automatically Track Certification Changes with Scrapegraphai, Gitlab and Rocket.chat — n8n GitLab workflow (18 nodes)
This n8n workflow provides automated CI/CD testing for Kubernetes applications using KinD (Kubernetes in Docker). It creates temporary infrastructure, runs tests, and cleans up everything automaticall
Triggers manually or on schedule (03:00 daily by default) Fetches workflows tagged via n8n API Normalizes workflow names and applies tag convention Prepares JSON in the same structure as an n8n UI exp
This workflow creates automated daily backups of your n8n workflows to a GitLab repository: Scheduled Trigger - Runs automatically at noon each day to initiate the backup process Fetch Workflows - Ret
Gitlab Code. Uses manualTrigger, noOp, splitInBatches, gitlab. Event-driven trigger; 21 nodes.
This template is inspired by Save your workflows into a GitHub repository by hikerspath and Back Up Your n8n Workflows To Github by jon-n8n.
v3.7. Uses executeCommand, gitlab, stickyNote. Webhook trigger; 19 nodes.
This workflow ensures that your self-hosted n8n workflows are version-controlled in a GitLab repository. It compares each current workflow from n8n with its stored counterpart in GitLab. If any differ
⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n ins
⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n ins
v3.6. Uses executeCommand, gitlab, stickyNote. Webhook trigger; 17 nodes.
Gitlab Filter. Uses manualTrigger, n8n, gitlab, stickyNote. Event-driven trigger; 16 nodes.
Automated Backup of n8n Workflows to GitLab Organized by Username. Uses n8n, gitlab, emailSend, httpRequest. Event-driven trigger; 16 nodes.
Fetches workflow definitions from within n8n, selecting only the ones that have one or more (configurable) assigned tags and then: Derives a suitable backup filename by reducing the workflow name to a
Claude Comment Handler v2. Uses executeCommand, gitlab. Webhook trigger; 15 nodes.
This n8n template automatically backs up your workflows to a GitLab repository whenever they're updated or activated, and generates README documentation using AI. This workflow can be aslo added as a
This solution ensures the secure backup and version control of your self-hosted n8n workflows by storing them in a GitLab repository. It compares current workflows with their GitLab counterparts, upda
Claude Comment Handler v3 - Happy Path. Uses executeCommand, gitlab. Webhook trigger; 13 nodes.
Claude Comment Handler. Uses executeCommand, gitlab. Webhook trigger; 13 nodes.
This n8n automation detects unused (“dead”) feature flags in an Android Kotlin/Java codebase by comparing your GitLab repository code against LaunchDarkly’s feature flag list.
Gitlab-Issue-Analyzer. Uses executeCommand, gitlab. Webhook trigger; 8 nodes.
Create An Issue On Gitlab On Every Github Release. Uses github, gitlab. Scheduled trigger; 6 nodes.
Create an issue on GitLab on every GitHub release. Uses github, gitlab. Scheduled trigger; 6 nodes.
Get Details Of A Gitlab Repository. Uses manualTrigger, gitlab. Event-driven trigger; 2 nodes.
25 of 25 workflows in this view · Browse all →
FAQ
How many n8n GitLab workflows are in the catalog?
25 n8n workflows in AutomationFlows currently use the GitLab integration — triggers, actions, or both.
How do I connect GitLab in n8n?
After importing the workflow JSON, n8n will prompt for GitLab credentials on the relevant nodes. AutomationFlows strips credential IDs before publishing — you'll add your own.
Can I combine these with other integrations?
Yes — most GitLab workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.