ENGINEERING
Datadog SLO breach freezes deploys and comments on open PRs
When a Datadog SLO drops below its error-budget target, blocks deploys by commenting a freeze status on every open GitHub pull request and notifying the team in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog SLO-alert webhookDatadog
- LogicConfirm breach is sustained, not flapping
- ActionList open GitHub pull requestsGitHub
- ActionComment freeze status on each open PRGitHub
- OutputSend freeze summary to SlackSlack
What it does
Uses Datadog as the SLO source and enforces the freeze at the pull-request level on GitHub. Rather than only flipping a label, it leaves a clear, dated comment on every open PR explaining that merges are paused due to error-budget exhaustion, so no one is surprised when their merge is blocked.
When to use it
Use it if your SLOs live in Datadog and your code is on GitHub, and you want the freeze message to reach contributors directly on their PRs instead of only in a channel they might mute.
How it works
- 1A Datadog SLO-alert webhook triggers the workflow when the budget target is breached.
- 2The workflow confirms the breach is below target and not a flapping recovery.
- 3It lists open pull requests on the affected GitHub repositories via the API.
- 4It posts a standardized freeze comment on each open PR with the SLO name and budget remaining.
- 5It sends a summary to Slack noting how many PRs were flagged and which repos are now frozen.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.