Detect unused Android feature flags with GitLab, LaunchDarkly, Jira & Slack
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 9 nodes and runs on a schedule (every week at 10:00). Along the way it connects GitLab, Google Sheets, Slack and Jira Software. It also calls app.launchdarkly.com over HTTP.
How it runs
Trigger: On a schedule (every week at 10:00).
- GitLab: uses GitLab
- Detect flags (Code): runs custom JavaScript code
- HTTP Request: calls app.launchdarkly.com
- Find dead flags (Code): runs custom JavaScript code
- Google Sheets: uses Google Sheets
- Check Dead Flags (If): checks a condition and branches into true / false
- Jira Software: uses Jira Software
- Slack: uses Slack
Services it uses
HTTP calls to: app.launchdarkly.com
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)
- If
n8n-nodes-base.if - Schedule Trigger
n8n-nodes-base.scheduleTrigger - GitLab
n8n-nodes-base.gitlab - Google Sheets
n8n-nodes-base.googleSheets - Slack
n8n-nodes-base.slack - Jira Software
n8n-nodes-base.jira - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code
From the author
Android Feature Flag Cleanup Bot (GitLab + LaunchDarkly) 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. It logs results in Google…