AI AGENTS
Slack command to instantly hand off your on-call page when you go offline
An on-call engineer types a Slack command to mark themselves unavailable, and the workflow finds the next in-hours responder, transfers any active PagerDuty incidents.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack command: mark me offlineSlack
- ActionLook up active incidents + rotationPagerDuty
- LogicSelect in-hours covering responder
- ActionReassign incidents + set overridePagerDuty
- OutputConfirm handoff in SlackSlack
What it does
Gives the current on-call engineer a one-line Slack command to declare themselves offline. The workflow immediately finds a covering responder whose local time is within working hours, transfers all of that engineer's active PagerDuty incidents, and confirms the handoff to everyone involved.
When to use it
Use it when responders need a fast, self-service way to bail out cleanly, for example losing connectivity, a family emergency, or end-of-shift. It avoids the manual dance of messaging a teammate and editing the schedule by hand mid-incident.
How it works
- 1An engineer invokes a Slack slash command declaring themselves unavailable.
- 2The workflow looks up that engineer's active PagerDuty incidents and rotation.
- 3A logic branch selects the next responder whose timezone is in working hours.
- 4It reassigns every active incident to the covering responder in PagerDuty.
- 5It applies a temporary schedule override so new pages also route correctly.
- 6It replies in Slack confirming the handoff and tagging the new owner.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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 AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.