CHATBOTS
Auto-Route Alerts to the Owning Team in Slack
When an alert fires, looks up the affected service's owner and on-call in the catalog and posts the runbook plus a direct page link to the responsible team's Slack channel within…
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident fires for a tagged servicePagerDuty
- ActionLook up owning team, channel, and runbook in the catalogPostgres
- LogicIf service is unmapped, fall back to platform on-call and flag gap
- ActionPost severity, on-call mention, and runbook to the owning channelSlack
- OutputWrite an audit row of the routing decisionPostgres
What it does
Closes the gap between an alert firing and the right humans seeing it. When PagerDuty raises an incident tagged with a service, this workflow looks that service up in the catalog and immediately posts to the owning team's Slack channel with the on-call handle, the runbook link, and a one-click acknowledge prompt.
When to use it
When alerts land in a generic firehose channel and responders waste minutes figuring out whose problem it is. Ideal once your catalog reliably maps services to teams and channels.
How it works
- 1A PagerDuty incident-triggered event arrives with the affected service identifier.
- 2The workflow queries the Postgres `service_catalog` for that service's owning team, Slack channel, and runbook.
- 3A logic step branches: if the service is unmapped, it falls back to the platform on-call channel and flags the gap.
- 4It posts a rich Slack message to the owning channel with severity, on-call mention, and runbook link.
- 5It writes an audit row recording which team was routed for later coverage analysis.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.