DEVOPS
Datadog Alert Severity Router to PagerDuty and Slack
Ingests Datadog monitor alerts, classifies severity from monitor priority and tags.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog monitor alert webhook receivedDatadog
- LogicParse priority, tags, and affected service
- LogicBranch on severity (P1/P2 vs low)
- ActionOpen PagerDuty incident and page on-callPagerDuty
- ActionPost low-urgency card to Slack triage channelSlack
- OutputReply in Slack thread with routing decisionSlack
What it does
This workflow receives every Datadog monitor alert webhook, reads the monitor priority and tags, and decides whether the alert deserves a page or just a heads-up. P1/P2 alerts open a PagerDuty incident and page the on-call engineer; everything else lands quietly in a Slack triage channel for async review.
When to use it
Run this when Datadog is paging your team for too many low-value alerts and you want a single gate that distinguishes wake-someone-up incidents from noise. Ideal for teams standardizing on Datadog monitors plus PagerDuty on-call rotations.
How it works
- 1A Datadog monitor transitions to alert and fires its webhook into the workflow.
- 2The workflow parses the payload for priority, tags, and the affected service.
- 3A severity branch checks whether priority is P1/P2 or carries a `pager:true` tag.
- 4For high severity, it opens a PagerDuty incident with the monitor link and triggers the matching escalation policy.
- 5For low severity, it posts a formatted card to the Slack triage channel instead.
- 6The final step writes the routing decision back as a Slack thread reply for an audit trail.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 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.