Build an AI Discord Moderation Bot: Ban, Kick, Timeout (No Code) | Quickchat AI - AI Agents<br>English Deutsch Español Français 日本語 Polski Português Svenska

Log in Start for free<br>Start for free

Solutions Use Cases<br>Customer Support Sales & Lead Generation Ecommerce IT & Internal Helpdesk Enterprise<br>Channels & Integrations<br>Website chat WordPress WhatsApp Discord Shopify Intercom Zendesk HubSpot All channels & integrations<br>Platform Releases Contact us

Why Us Pricing Resources About us Case Studies Careers Blog Affiliate Program Legal Documentation Status Contact<br>Log in Start for free

{t.navigation.log_in}

{t.navigation.book_a_demo}

-->

Build an AI Discord Moderation Bot: Ban, Kick, Timeout (No Code)<br>Piotr Grudzień on June 25, 2026 • 30 min read

Your AI Agent already talks to your community on Discord. This guide turns it into an AI Discord moderation bot , no code required. With a handful of custom AI Actions , a moderator types “timeout @spammer for 10 minutes”, “ban @user for scam links”, or “set slowmode in #general to 30 seconds”, and the Agent performs the action through the Discord API, from plain language.

We make conversational Agents, not slash-command bots. So the goal here is not to rebuild a classic rule-based moderation bot like MEE6 or Dyno (how Quickchat compares). It is to let a moderator drive moderation in plain language , with the Agent translating intent into the right Discord API call, asking for confirmation before anything destructive, and writing a reason to the audit log every time.

You need two things, both free:

a Quickchat AI Agent (sign up here and use for free ), connected to your Discord server

a Discord server where you are an admin

The mechanism is AI Actions : custom HTTP requests your Agent makes during a conversation. There is no one-click Discord moderation pack; you add these actions by hand. It is the same approach as wiring an Agent to the Telegram Bot API or to Google Sheets, pointed at Discord. By the end you will have seven working actions , with the destructive ones locked to admins by a deterministic gate (a run-condition on a Discord-verified flag, so a prompt can never talk the bot past it), and you will have tested each one yourself .

This is a long, exact walkthrough. The canonical reference for AI Actions lives in the docs at docs.quickchat.ai/ai-agent/actions.

The screenshots below come from a test Agent called Orbit , the moderation co-pilot for a fictional community server, Nebula Lounge . The server is invented so the example stays neutral, but every conversation, every API call, and every effect shown here was produced by a real Agent running the real reply pipeline against a real Discord server. Use your own server’s details when you follow along.

What you will build

Seven actions, grouped into three jobs. Two of them (kick and ban) are destructive, so the Agent will confirm before running them.

GroupActionWhat the moderator saysDiscord callModerationtimeout_member”timeout @user for 10 minutes”PATCH guild memberModerationkick_member”kick @user” (destructive)DELETE guild memberModerationban_member”ban @user” (destructive)PUT guild banModerationunban_member”unban 123…”DELETE guild banRolesassign_role”give @user the Verified role”PUT member roleServerset_slowmode”set slowmode in #general to 30s”PATCH channelServersend_announcement”post in #announcements: …”POST channel message

Each action is a described HTTP request the Agent can call during a conversation.

A chat message can come from anyone, so the natural worry is whether a regular member could talk the bot into banning someone. They cannot. The destructive actions are locked to admins by a run-condition on a Discord-verified flag, evaluated on our side before any request goes out, never by the prompt. You wire that gate in Step 7.

The same building blocks reach past a moderator co-pilot. With one more piece you can let the whole community talk to the Agent: little games and challenges where saying the right thing earns a reward, like a self-claim role behind a passphrase. We build a safe version at the end, in Going further.

How AI Actions call Discord, and how your server’s values flow in

An AI Action is a described HTTP request. When the Agent decides an action applies, it fills in the parameters and Quickchat sends the request. Three pieces of information have to reach Discord, and they arrive in three different ways .

The token comes from the connected bot, the server ID from the live conversation, and the target from the moderator’s message. You wire each one once.

1. The bot token comes from a System Token. Discord authenticates every request with your bot token. You do not paste it into each action. Once your bot is connected in the Discord integration, the token is available as the System Token {{discord_bot_token}}. Select it from the Add AI Data menu and put it in the Authorization header. It is injected into the outgoing request at send time, and it is never exposed to...