CHATBOTS
On-Call Handoff Digest at Rotation Boundary
When a PagerDuty on-call rotation changes hands, this bot assembles every open incident, active alert, and unresolved Slack thread into a single handoff digest and posts it…
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty on-call handoff eventPagerDuty
- ActionFetch open + acknowledged incidentsPagerDuty
- ActionQuery firing Datadog monitors for owned servicesDatadog
- ActionScan channel for unresolved threadsSlack
- LogicBranch on whether anything is open vs clean handoff
- OutputPost handoff digest to incoming on-callSlack
What it does
At the moment a PagerDuty schedule rotates, this bot gathers the full operational state the outgoing engineer was holding and hands it to the incoming one. No more 'so, anything I should know?' over a hurried Slack DM. The digest lists open incidents with current status, firing Datadog monitors, and any Slack threads still waiting on a human reply.
When to use it
Run this on any team with a recurring on-call rotation where context regularly gets dropped at handoff. It is most valuable for teams whose pages span multiple services and where a single Slack channel accumulates half-finished investigation threads.
How it works
- 1PagerDuty fires its `on_call_handoff` event when the schedule boundary is reached.
- 2The bot pulls all open and acknowledged incidents for the affected escalation policy from PagerDuty.
- 3It queries Datadog for monitors currently in Alert or Warn state on the owned services.
- 4It scans the incident channel for threads with no reply in the last interval, flagging them as unresolved.
- 5A branch checks whether anything is actually open; if all clear, it posts a short 'clean handoff' note instead.
- 6The assembled digest is delivered as a direct message and channel post to the incoming on-call engineer.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect DatadogMetrics, traces, log search.
- 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 Chatbots workflows
Discord Onboarding Completion to CRM Sync
The moment a member finishes Discord onboarding, captures their submitted profile answers, creates or updates a contact in HubSpot.
Discord FAQ-Gated Role Concierge
Greets each new Discord member in a private onboarding thread, walks them through required FAQ steps one at a time.
Discord FAQ Free-Text Answer Grader
When a member submits a free-text answer in their onboarding thread, an agent grades it against the canonical FAQ knowledge base, replies with targeted feedback.
Discord verify-button onboarding via web form webhook
Receives a completed external verification form by webhook, matches it to the Discord account, grants the verified role, and confirms back to the member in Discord.
Discord intro-gated role granting concierge
Watches your #introductions channel, uses AI to confirm a new member's intro is genuine and complete, then auto-assigns the verified Member role and welcomes them.
Daily Discord Digest of Repeated WAF False-Positive Reports
Each morning, scans logged Discord WAF reports in Postgres, groups them by the Cloudflare rule that keeps firing.
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.
