DEVOPS
Gate Release Tags Against Recent Incident History
When a release tag is pushed, it pulls the last 30 days of incidents for the affected services and posts a go/hold recommendation to Slack based on how unstable those services…
How it runs
The automated pipeline, trigger to output.
- TriggerRelease tag published (GitHub webhook)GitHub
- ActionRead release notes and affected servicesGitHub
- ActionPull 30-day incident history for servicesPagerDuty
- LogicScore stability and decide go / hold
- OutputPost go/hold recommendation to SlackSlack
What it does
On a new release tag, this workflow checks how stable the services in that release have been lately by querying recent incidents, then recommends shipping now or holding for a calmer window — delivered to Slack so the release captain decides with data.
When to use it
Use it when you ship from git tags and want to avoid stacking a new release on top of services that are still firefighting from last week's outages.
How it works
- 1A GitHub release webhook fires when a tag is published.
- 2The flow reads the release notes and changed services from the tag.
- 3A PagerDuty step pulls incidents for those services over the last 30 days.
- 4A scoring step combines incident count, severity, and recency into a stability score.
- 5A branch decides go vs. hold based on the threshold.
- 6The recommendation, with the incidents that drove it, is posted to the release Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.