AI AGENTS
Weekly Discord Moderation Digest
On a weekly schedule, an agent reads the past week's case log from Notion, summarizes moderation trends and repeat offenders.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery last 7 days of cases from NotionNotion
- ActionAggregate trends and repeat offendersOpenAI
- ActionArchive full digest report in NotionNotion
- OutputPost highlights digest to mod channelDiscord
What it does
Gives the mod team a recurring pulse on community health. Once a week the agent reads every case logged in the past seven days, rolls them up by category and severity, surfaces repeat offenders and any spike in a violation type, and writes a readable digest — total actions, top issues, watch-list members, and week-over-week change.
When to use it
Use it when leadership wants visibility into moderation load and trends without digging through logs, or when you need an early signal that a rule is being broken more often. It turns the raw case log into a decision-ready weekly briefing.
How it works
- 1A weekly schedule triggers the flow.
- 2The agent queries the last seven days of cases from the Notion case log.
- 3An OpenAI step aggregates the data into trends, repeat-offender lists, and a narrative summary.
- 4The agent archives the full digest as a new report page in Notion.
- 5A condensed version is posted to the mod channel so the team sees highlights at a glance.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect NotionPages, databases, comments.
- 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
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.