DEVOPS
Freeze deploys and page on-call when error budget burns fast
When Datadog fires a fast-burn SLO alert via webhook, this workflow flips a deploy-freeze flag, comments the freeze on open release PRs in GitHub.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog fast-burn webhookDatadog
- LogicParse service, burn multiplier, budget
- ActionSet deploy-freeze flag in PostgresPostgres
- ActionComment freeze on open release PRsGitHub
- OutputPage service owner in PagerDutyPagerDuty
What it does
Reacts to a fast-burn alert by automatically declaring a deploy freeze for the affected service. It records the freeze, signals it on in-flight release pull requests so nobody merges into a burning service, and escalates to the right responder.
When to use it
Use it when a sudden spike can blow your monthly budget in hours and you need an enforced freeze rather than a polite Slack note. Best for services with a strict error-budget policy and clear ownership.
How it works
- 1A Datadog fast-burn SLO monitor sends a webhook to the flow.
- 2A logic step parses the alert to extract the service, current burn multiplier, and remaining budget.
- 3The flow sets the per-service deploy-freeze flag in a Postgres control table other gates read.
- 4It posts a freeze comment on open release-labeled GitHub PRs for that service.
- 5It opens a PagerDuty incident routed to the service owner with the budget figures attached.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect PostgresAny Postgres URL — query, write, migrate.
- 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.