DEVOPS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog monitor alertDatadog
- LogicDedupe against open PagerDuty incidentsPagerDuty
- ActionCreate Zoom war-room bridgeZoom
- ActionOpen PagerDuty incident with linkPagerDuty
- OutputAnnounce war-room in SlackSlack
What it does
Datadog can fire dozens of correlated alerts during one outage. This workflow listens for critical monitor alerts, suppresses duplicates that belong to an incident already in flight, and for a truly new event spins a Zoom war-room and a tracking PagerDuty incident — preventing a wall of redundant bridges.
When to use it
Use it when Datadog is your primary alerting source and you want exactly one war-room per outage, not one per noisy monitor. Ideal for teams drowning in alert fan-out.
How it works
- 1A Datadog webhook fires on a monitor entering the alert state.
- 2A dedupe step checks PagerDuty for an open incident matching the affected service; if found, it just adds a note and stops.
- 3For a new outage, Zoom creates the war-room bridge.
- 4PagerDuty opens an incident keyed to the service and attaches the bridge link.
- 5Slack announces the new war-room with the alert metric, current value, and join link.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect ZoomMeetings, recordings, transcripts.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.
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.
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-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.