AI AGENTS
Discord FAQ Agent with Slack Mod Escalation
Drafts Discord answers from pinned docs, and routes every question it can't confidently answer into a triaged Slack channel for the staff team, complete with the member's question.
How it runs
The automated pipeline, trigger to output.
- TriggerNew message in Discord support channelDiscord
- ActionRetrieve relevant docs from NotionNotion
- LogicDo the docs cover this question?
- ActionPost sourced AI reply in DiscordDiscord
- OutputRoute unknowns to Slack staff channel with draftSlack
What it does
This agent keeps the answering loop in Discord but moves the escalation queue to where your staff actually work: Slack. When a question isn't covered by the docs, it doesn't clutter the community with a mod thread — it files a clean, contextual ticket in a private Slack channel with a suggested reply your team can edit and approve.
When to use it
Ideal when your moderators live in Slack, not Discord, and you want community members to never see the internal escalation churn. Good fit for teams with a formal on-call or support rotation.
How it works
- 1A new Discord message triggers the agent.
- 2It retrieves the relevant pinned docs from Notion.
- 3A confidence gate decides whether the docs cover the question.
- 4Covered questions get a sourced AI reply posted directly in Discord.
- 5Uncovered questions are packaged — original text, member, channel link, and a suggested draft — and routed to a private Slack staff channel.
- 6Staff approve or edit in Slack; the final answer can be posted back to the Discord thread.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect NotionPages, databases, comments.
- 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.