AI AGENTS
Discord Moderation Daily Slack Digest
On a daily schedule, the agent reads the day's moderation cases from Postgres, summarizes warnings and escalations, and posts a clean digest to the mod team's Slack channel.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionQuery last 24h of moderation casesPostgres
- ActionAggregate by category, outcome, and open escalations
- ActionAgent writes plain-language digest
- OutputPost digest to mod Slack channelSlack
What it does
Gives leadership a once-a-day readout of community health without anyone scrolling Discord logs. The agent pulls the last 24 hours of moderation cases, groups them by outcome and channel, calls out trends and any unresolved escalations, and drops a tidy summary into Slack.
When to use it
When mod work happens in Discord but the people who need oversight live in Slack. Use this for a daily standup-style recap that flags spikes in abuse, names recurring offenders, and lists cases still awaiting a human decision.
How it works
- 1A daily schedule fires at your chosen time.
- 2The agent queries Postgres for all moderation cases logged in the past 24 hours.
- 3It aggregates counts by category and outcome, and flags open escalations still pending review.
- 4The agent writes a plain-language digest with the day's highlights and trend callouts.
- 5It posts the formatted digest to the moderation team's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.