DEVOPS
Discord On-Call Takeover Brief on PagerDuty Rotation Change
When PagerDuty rotates the on-call to a new engineer, posts a personalized takeover brief in Discord with active pages, recent acknowledgments, and unresolved follow-ups.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty rotation change webhookPagerDuty
- ActionFetch open and acked incidents from PagerDutyPagerDuty
- LogicSplit into handed-off vs newly assigned
- ActionResolve incoming engineer Discord IDDiscord
- OutputPost takeover brief mentioning engineerDiscord
What it does
Listens for PagerDuty on-call rotation events and immediately direct-messages or posts a takeover brief in Discord for the engineer coming on duty. The brief lists pages still open, anything acknowledged but not resolved by the outgoing engineer, and links back to each incident so nothing silently transfers.
When to use it
Use it when PagerDuty owns your escalation policy and you want the rotation change itself to trigger the handoff, rather than a fixed clock time. It suits teams with overlapping or irregular rotations where shift boundaries are not predictable.
How it works
- 1A PagerDuty webhook fires on the on-call rotation change event.
- 2The flow fetches currently open and acknowledged incidents from PagerDuty.
- 3A logic step splits incidents into unresolved-handed-off versus newly assigned.
- 4It maps the incoming engineer to their Discord user ID.
- 5The takeover brief is posted to Discord, mentioning the incoming engineer.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect DiscordCommunity channels + voice + bots.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.