CHATBOTS
Shift Handoff to a Notion Runbook Page
On a schedule near the end of each on-call shift, this bot compiles open alerts and in-flight incidents into a structured Notion handoff page so the next engineer has a durable.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires before shift boundary
- ActionPull open + recent incidents from PagerDutyPagerDuty
- ActionFetch non-OK Datadog monitorsDatadog
- ActionCreate dated Notion handoff pageNotion
- OutputNotify incoming engineer with page linkSlack
What it does
This bot writes the on-call handoff into Notion as a dated, structured page rather than a chat message that scrolls away. It collects the shift's open work from PagerDuty and Datadog, organizes it into sections (active incidents, watch items, follow-ups), and creates a Notion page the incoming engineer can read, edit, and reference all shift long.
When to use it
Choose this over a Slack-only digest when your team wants an auditable handoff history, or when incidents commonly span multiple shifts and need a living document that each engineer updates in turn.
How it works
- 1A schedule fires 30 minutes before the configured shift boundary.
- 2The bot pulls open and recently-resolved incidents from PagerDuty for the rotation's escalation policy.
- 3It fetches Datadog monitors in a non-OK state to populate the 'watch items' section.
- 4The collected data is shaped into titled sections with status, links, and timestamps.
- 5A new Notion page is created under the team's handoff database, dated and tagged with the incoming engineer.
- 6A short Slack notice links to the freshly created Notion page so the next engineer knows it is ready.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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 Chatbots workflows
Discord WAF False-Positive Triage from Ray ID
When a user posts a Cloudflare ray ID in a Discord support channel, the bot looks up the blocked request's WAF event, classifies whether it looks like a genuine false positive.
Agentic WAF Investigator with Discord Approval Gate
An autonomous agent investigates a Discord-reported WAF block end to end: pulls Cloudflare logs, correlates with PagerDuty incidents, decides if an allowlist is safe.
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.
Draft WAF Allowlist Proposal to Linear from Discord Report
Lets a support engineer confirm a Discord WAF report is a false positive, then auto-drafts a scoped Cloudflare allowlist rule proposal and files it as a Linear ticket…
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 FAQ-Gated Role Concierge
Greets each new Discord member in a private onboarding thread, walks them through required FAQ steps one at a time.
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.