CHATBOTS

Discord Repeat-Offender Daily Pattern Digest

Runs each morning to query the offender ledger for users whose violations are accelerating, summarizes the pattern with an LLM, and posts a ranked digest to the moderator channel.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionQuery offender ledger for trailing-week offensesPostgreSQLPostgres
  • LogicKeep users above threshold or trending up
  • ActionSummarize each offender's pattern with OpenAIOpenAI
  • OutputPost ranked risk digest to moderator channelDiscordDiscord

What it does

On a daily schedule, this scans the Postgres offender ledger and surfaces the users who matter: those crossing a strike threshold, or whose offense rate is climbing day over day. An LLM turns the raw rows into a readable narrative per user, and the bot posts a ranked digest so the mod team starts the day knowing exactly who to watch.

When to use it

Use it when individual offenses are already logged but nobody reviews the aggregate. Single warnings rarely reveal a pattern; this catches the slow-burn repeat offender before they require an emergency ban.

How it works

  1. 1A daily schedule trigger fires at your chosen hour.
  2. 2A Postgres query pulls every user with offenses in the trailing 7 days plus their prior-week counts.
  3. 3A logic step keeps only users above the strike threshold or showing an upward trend.
  4. 4An OpenAI call writes a short pattern summary for each flagged user, citing their worst categories.
  5. 5The bot posts a ranked digest (highest risk first) to the moderator channel for the morning review.

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
    Connect OpenAIModels, embeddings, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.