DEVOPS
Mid-Shift Recap When a Sev-1 Escalates Overnight
When a high-urgency PagerDuty incident escalates to a second responder, immediately gathers the live timeline and Datadog signals and posts a real-time situation recap to Discord…
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident escalation webhookPagerDuty
- LogicFilter to high-urgency incidents only
- ActionFetch live timeline and respondersPagerDuty
- ActionPull latest Datadog metricsDatadog
- ActionWrite current-state recap with LLMOpenAI
- OutputPost recap to Discord war roomDiscord
What it does
This is the in-the-moment version of a handoff. When a Sev-1 incident escalates — meaning the first responder needed backup — it instantly compiles what has happened so far: the timeline, current acknowledgers, affected service, and the relevant Datadog graphs. It posts a tight situation recap so whoever just got pulled in is up to speed in seconds, not after ten minutes of scrollback.
When to use it
Use it for critical incidents where escalation means a fresh engineer is joining mid-fire. It removes the cold-start delay during the worst moments by handing the new responder a current picture immediately.
How it works
- 1A PagerDuty webhook fires on an incident escalation event.
- 2A logic step filters to high-urgency incidents only, ignoring routine reassignments.
- 3Fetch the live incident timeline and current responders from PagerDuty.
- 4Pull the latest Datadog metrics for the impacted service.
- 5An LLM writes a concise current-state recap.
- 6Post the recap to the incident's Discord war-room channel.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect DiscordCommunity channels + voice + bots.
- 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.