DEVOPS
On-demand removal MR for a single flag via Slack command
An operator names a flag in Slack; the workflow checks it has been fully rolled out 90+ days, then opens a GitLab removal MR assigned to its owner and replies with the link.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack slash command with flag keySlack
- ActionLoad flag rollout and metadataPostgres
- LogicGate on 90-day safety check
- ActionOpen removal MR and assign ownerGitLab
- OutputReply with MR link in threadSlack
What it does
Gives operators a one-shot, on-demand path to retire a specific flag. Triggered by a Slack slash command carrying a flag key, it validates the flag is genuinely safe to remove (fully rolled out for 90+ days, not experiment-tagged), opens a GitLab removal MR assigned to the owner, and replies in the thread with the MR link.
When to use it
Use it when an engineer already knows the exact flag to kill and does not want to wait for the weekly batch. It enforces the same 90-day safety check as the scheduled sweep, so manual cleanup can't skip the guardrail.
How it works
- 1A Slack slash command with a flag key triggers the workflow via webhook.
- 2A Postgres query loads that flag's rollout percentage, last-changed date, owner, and tags.
- 3A logic gate rejects the request if the flag is below 100%, younger than 90 days, or experiment-tagged, replying with the reason.
- 4If it passes, a GitLab action opens the removal MR and assigns the owner.
- 5A Slack reply posts the MR link back into the originating thread.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.