AI AGENTS
Discord Report Triage Agent
When a member files a /report or reacts with a flag, an agent reads the offending message in context, classifies the violation against your rules.
How it runs
The automated pipeline, trigger to output.
- TriggerMember files /report or flag reactionDiscord
- ActionFetch reported message + surrounding contextDiscord
- ActionClassify violation against community rulesOpenAI
- LogicBranch: no-action vs needs-human-review
- OutputPost triage card to moderator channelDiscord
What it does
Turns raw member reports into structured, pre-triaged cases. Instead of mods scrolling back through a channel to figure out what happened, the agent pulls the reported message plus surrounding context, judges it against your written community rules, and posts a clean triage card to the moderator channel with a category (spam, harassment, NSFW, off-topic, none) and a confidence score.
When to use it
Use it when your server gets more reports than your mod team can read carefully, or when reports arrive without enough context to act on. It removes the first 60 seconds of every moderation decision and keeps borderline cases visible instead of buried.
How it works
- 1A member triggers a `/report` slash command or flag reaction in Discord, firing a webhook.
- 2The agent fetches the reported message and the few messages around it for context.
- 3An OpenAI classification step scores the content against your rule set and assigns a category and severity.
- 4A branch separates clear no-action cases (auto-closed) from cases that need a human.
- 5Actionable cases are posted as a triage card to the moderator review channel in Discord, tagged by severity.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect OpenAIModels, embeddings, files.
- 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.