DEVOPS
Kill the most recent flag rollout when PagerDuty opens an incident
When a high-urgency PagerDuty incident opens, it correlates the incident time with active flag rollouts, disables the most recently changed flag via GitHub.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty webhook on new high-urgency incidentPagerDuty
- ActionFind recent flag rollouts in incident lookback window via GitHubGitHub
- LogicBranch: exactly one correlating rollout?
- ActionDisable the suspect flag via GitHub commitGitHub
- ActionAnnotate PagerDuty incident with the suspect flagPagerDuty
- OutputNotify responders in SlackSlack
What it does
Treats a fresh production incident as a signal to undo the last thing you changed. It finds the flag that ramped just before the incident, turns it off, and annotates the incident with that hypothesis.
When to use it
Use when flag changes are your most frequent production variable and you want incident response to automatically test the obvious culprit first, shaving minutes off mean-time-to-recovery.
How it works
- 1A PagerDuty webhook fires on a new high-urgency incident.
- 2A GitHub action reads recent flag-config commits to find rollouts that advanced within the incident's lookback window.
- 3A logic branch checks whether exactly one recent rollout correlates; if zero or many, it skips the auto-kill and only annotates.
- 4When a single suspect exists, a GitHub commit disables that flag.
- 5A PagerDuty note is added to the incident naming the disabled flag and the correlating commit.
- 6A Slack message alerts responders that an automatic rollback was attempted.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect GitHubRepos, issues, pull requests, 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
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.