AI AGENTS

Discord Repeat-Offender Escalation Router

On each new warning, the agent counts a member's prior strikes in Postgres and opens a dedicated human-mod review thread for anyone who crosses the repeat-offender threshold.

CategoryAI Agents
Enginepaperclip
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew warning record createdPostgreSQLPostgres
  • ActionQuery member's prior strike historyPostgreSQLPostgres
  • LogicBranch on repeat-offender threshold
  • ActionAgent summarizes offense history
  • OutputOpen tagged mod-review thread in DiscordDiscordDiscord

What it does

Watches the running strike history of every member. When someone receives a new warning, the agent tallies their past violations, and if they've crossed your repeat-offender line it spins up a focused review thread for the mod team with the full history attached, so humans decide on a mute or ban with full context.

When to use it

When first offenses are routine but repeat behavior needs a human judgment call. Use this so chronic rule-breakers automatically surface to moderators with their record laid out, instead of slipping through because no one connected the dots across weeks of incidents.

How it works

  1. 1A new warning record is written, triggering the workflow.
  2. 2The agent queries Postgres for all prior warnings tied to that member.
  3. 3A branch checks whether the strike count meets the escalation threshold.
  4. 4Below threshold, it updates the member's tally and exits quietly.
  5. 5At or above threshold, the agent summarizes the offense history and opens a dedicated Discord mod-review thread, tagging the on-call moderators for an action decision.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.