DEVOPS
Morning On-Call Handoff Brief to Microsoft Teams
Every morning at shift change, pulls the last 12 hours of PagerDuty incidents and Datadog alerts, summarizes them into a structured handoff brief.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires at morning shift change
- ActionFetch last 12h of PagerDuty incidentsPagerDuty
- ActionFetch Datadog alerts and recoveriesDatadog
- ActionSummarize and prioritize events with LLMOpenAI
- OutputPost handoff brief to Teams on-call channelMicrosoft Teams
What it does
Generates a single, skimmable handoff brief at the start of each day shift. It gathers everything that fired overnight — PagerDuty incidents and Datadog monitor alerts — and turns the noise into one organized message so the incoming on-call engineer knows exactly what happened while they slept and what still needs attention.
When to use it
Run this when your team rotates on-call at a fixed time each morning and the incoming engineer currently has to dig through PagerDuty, Datadog, and chat history to reconstruct the night. It replaces that manual archaeology with a consistent brief.
How it works
- 1A schedule fires at the daily shift-change time (e.g. 8:00 AM).
- 2Fetch all PagerDuty incidents triggered, acknowledged, or resolved in the last 12 hours.
- 3Fetch Datadog monitor alerts and recoveries over the same window.
- 4An LLM step groups events by service, flags anything still open, and writes a prioritized summary with severity and current status.
- 5Post the formatted brief to the on-call Microsoft Teams channel, with still-open items pinned at the top.
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 Microsoft TeamsChannels, chats, files.
- 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
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.
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…
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.
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.
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.
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.