DEVOPS
Schedule a 30-day removal reminder when a flag hits 100%
When your flag platform fires a webhook that a flag reached 100% rollout, this records the date and, 30 days later, checks it's still fully on and opens a cleanup PR.
How it runs
The automated pipeline, trigger to output.
- TriggerFlag platform webhook on 100% rolloutHTTP webhook
- ActionRecord flag and completion date in PostgresPostgres
- LogicAfter 30 days, re-check flag is still fully onDatadog
- ActionOpen GitHub removal PR for the matured flagGitHub
- OutputMark the tracking row as cleaned upPostgres
What it does
Instead of scanning everything weekly, this workflow reacts the instant a flag finishes rolling out. When your feature-flag system posts a webhook saying a flag hit 100%, it stamps the completion date in a tracking table. A companion check 30 days later confirms the flag is still fully on and untouched, then opens the cleanup PR — so each flag gets exactly one timely removal nudge.
When to use it
Use it when you want flag cleanup driven by the actual rollout event rather than a calendar sweep, and when your flag platform can emit webhooks on rollout state changes. It produces less noise than a periodic scan because each flag is evaluated on its own 30-day timer.
How it works
A webhook from the flag platform triggers on a 100% rollout event, and the workflow upserts the flag and completion date into a Postgres tracking table. A scheduled sweep reads rows that crossed the 30-day mark, re-checks current state in Datadog, and for any flag still pinned at 100% with no change it opens a GitHub removal PR and marks the row done.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect DatadogMetrics, traces, log search.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.