DEVOPS
Auto-archive a shipped flag when its cleanup PR merges
When a flag-removal pull request is merged in GitHub, this archives the corresponding flag in the provider and posts a confirmation in the team Slack channel so the flag and its…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull request mergedGitHub
- LogicConfirm it's a cleanup PR and extract the flag key
- ActionArchive the flag in the providerHTTP webhook
- OutputPost retirement confirmation to SlackSlack
What it does
Closes the loop on flag retirement. The moment a cleanup PR is merged, it parses the flag key from the PR, archives that flag in your flag provider so it can no longer be evaluated, and announces the retirement in Slack. This guarantees the flag definition and the code that read it are removed in the same beat — no orphaned flags left live after the code is gone.
When to use it
Use it as the merge-side counterpart to a cleanup sweep. Ideal for teams that delete flag code in PRs but keep forgetting to archive the flag itself in the dashboard, leaving dead flags evaluating forever.
How it works
- 1A GitHub pull-request-merged event triggers the flow.
- 2A logic step confirms the PR is a flag-cleanup PR and extracts the flag key from its body or branch.
- 3An HTTP call archives that flag in the provider.
- 4Slack posts a retirement confirmation with the PR and flag key to the team channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.