AI AGENTS
Discord moderation decisions logged to a Notion case file
On a schedule, an agent sweeps the pending moderation queue, drafts a decision and rationale for each open case.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled sweep of the moderation queue
- ActionRead unresolved reports from DiscordDiscord
- ActionClassify each message with Hugging FaceHugging Face
- LogicSkip resolved or below-threshold cases
- ActionAgent drafts decision + rationale per case
- OutputUpsert case files to Notion log, status Awaiting reviewNotion
What it does
Runs a recurring sweep of unresolved Discord reports and converts each into a permanent, searchable Notion case file. For every open case the agent records the message, its classification, the recommended action, and a written rationale — then marks the row "Awaiting review" so a moderator approves or overrides directly in Notion.
When to use it
Use it when you need a durable moderation record for appeals, transparency reports, or compliance, and you'd rather review a batch in one Notion view than chase individual Discord threads. Good for teams that already run their ops out of Notion.
How it works
- 1A scheduled trigger fires every few hours.
- 2The agent reads all unresolved reports from the Discord moderation queue.
- 3A Hugging Face classifier categorizes each flagged message by violation type.
- 4Logic skips cases already resolved or below the action threshold.
- 5For each remaining case the agent drafts the decision, action, and rationale.
- 6It upserts a structured row into the Notion moderation database with status "Awaiting review".
- 7A Discord ping links moderators to the new Notion rows needing sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect NotionPages, databases, comments.
- 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
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.
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.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
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.
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.
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.
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.