AI AGENTS
Discord Warning Appeal Intake Agent
When a warned member submits an appeal via webhook form, the agent pulls the original case from Postgres, assesses the appeal against it.
How it runs
The automated pipeline, trigger to output.
- TriggerAppeal form submitted via webhookHTTP webhook
- ActionLook up original warning case in PostgresPostgres
- ActionAgent assesses appeal against evidence
- ActionDraft uphold/reduce/overturn recommendation
- OutputPost case + recommendation to mod channelDiscord
What it does
Gives members a structured way to contest a warning and gives mods a pre-analyzed case. When an appeal comes in, the agent matches it to the original moderation record, weighs the member's explanation against the logged evidence, and posts a clear uphold-or-overturn recommendation that a human makes the final call on.
When to use it
When appeals arrive scattered across DMs and tickets with no link to the original incident. Use this to standardize intake through a form, automatically reunite each appeal with its source case, and hand mods a reasoned starting point instead of a cold re-investigation.
How it works
- 1An appeal form submission hits an incoming webhook.
- 2The agent looks up the referenced warning and its evidence in Postgres.
- 3It compares the member's appeal text against the original verdict and context.
- 4The agent drafts a recommendation (uphold, reduce, or overturn) with its reasoning.
- 5It posts the appeal, original case, and recommendation to the Discord mod review channel for a final human decision.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect DiscordCommunity channels + voice + bots.
- 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
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.