AI AGENTS
On-Call Shift Handoff Briefing from Honeycomb and Open Incidents
On a schedule at each shift change, the agent summarizes Honeycomb anomaly trends and open PagerDuty incidents into a single on-call handoff briefing posted to Slack…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled shift-change time
- ActionQuery Honeycomb anomaly trendsHoneycomb
- ActionPull open PagerDuty incidentsPagerDuty
- LogicGroup by service and rank watch items
- OutputPost handoff briefing to SlackSlack
What it does
Generates a clean shift-handoff brief so the incoming on-call engineer starts informed. The agent reviews the last shift's Honeycomb anomalies, lists still-open PagerDuty incidents, and flags services trending toward trouble — turning tribal knowledge into a written handoff.
When to use it
Use it for rotations where context is lost between shifts and the new on-call discovers problems only when they page. Schedule it to run a few minutes before each handoff window.
How it works
- 1A scheduled trigger fires at the shift-change time.
- 2The agent queries Honeycomb for anomalies and slow-burning trends over the shift window.
- 3It pulls open and recently resolved incidents from PagerDuty.
- 4Logic groups findings by service and ranks watch items by risk.
- 5It composes a concise handoff brief with explicit things-to-watch.
- 6It posts the briefing to the on-call Slack channel and tags the incoming engineer.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.