AI AGENTS
Discord Channel Toxicity Hourly Sweep
On an hourly schedule, the agent samples recent messages across busy Discord channels, scores them for toxicity, logs incidents to Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule fires
- ActionFetch recent messages from watched channelsDiscord
- ActionAgent scores conversation toxicity
- ActionLog flagged incidents to PostgresPostgres
- LogicBranch on channel heat threshold
- OutputOpen mod thread with draft warningsDiscord
What it does
Proactively patrols active channels instead of waiting for reports. Each hour the agent pulls recent messages from your high-traffic channels, scores the conversation for toxicity and pile-ons, records flagged incidents, and when a channel gets heated it opens a mod thread with draft warnings for the worst actors.
When to use it
When harmful behavior often goes unreported because no one bothers to flag it, or when a single channel can boil over fast during drama. Use this as an always-on patrol that catches rising toxicity early and gives mods a ready-to-act thread before things spiral.
How it works
- 1An hourly schedule fires the sweep.
- 2The agent fetches recent messages from the configured set of Discord channels.
- 3It scores each channel's conversation for toxicity and identifies the worst messages.
- 4Flagged incidents are written to Postgres for the audit trail.
- 5A branch checks whether any channel crossed the heat threshold; if so, the agent opens a mod thread with draft warnings; otherwise the sweep ends quietly.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.