CHATBOTS
Error-Budget Brief for the Incoming On-Call
At rotation boundary, this bot pairs unresolved Sentry issues with PagerDuty incident history to brief the incoming engineer on which services are burning error budget and most…
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty handoff eventPagerDuty
- ActionPull unresolved Sentry issues by volumeSentry
- ActionFetch trailing page count per servicePagerDuty
- LogicJoin sources; score paging likelihood into tiers
- OutputPost risk brief with Sentry deep links to SlackSlack
What it does
This bot gives the incoming on-call a risk-forward briefing instead of a backward-looking incident dump. It correlates unresolved Sentry issues with recent PagerDuty page frequency to surface which services are degrading and likely to alert during the upcoming shift, so the engineer knows where to keep an eye before anything pages.
When to use it
Use this when your team wants handoffs to be predictive rather than reactive — especially when certain services have been flaky and you want the next engineer primed on the highest-risk areas rather than reading raw alert lists.
How it works
- 1PagerDuty fires the on-call handoff event at the rotation boundary.
- 2The bot pulls unresolved Sentry issues ranked by event volume and regression status.
- 3It fetches the trailing page count per service from PagerDuty incident history.
- 4A logic step joins the two sources and scores each service's likelihood of paging this shift.
- 5Services are sorted into a 'watch closely' tier and an 'informational' tier.
- 6The risk brief is posted to the incoming engineer in Slack with deep links to each Sentry issue.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect SentryErrors, performance, releases.
- 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.