Browse the docs

Agent setup guide

Discord Community Assistant

Answers your Discord members' questions from your FAQ in a thread and flags bugs, spam and rule breaks to moderators.

Available About 15 min to set up

What it does

Answers your Discord members' questions from your FAQ in a thread and flags bugs, spam and rule breaks to moderators.

  • Reads each new message in the Discord channel you pick (checked on your plan's schedule interval).
  • AI sorts it: question, bug report, rule break or spam, or chatter.
  • Answers questions your FAQ covers in a thread on the message, using only your FAQ.
  • Posts bug reports, rule breaks, spam and questions the FAQ doesn't cover to your private moderators' channel with a link.
  • Leaves chatter and bot messages alone.

What it needs

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • Discord, connected in Settings → Integrations, with your bot in the server.

What it doesn't do

  • It never deletes messages, mutes, kicks or bans: moderators act on what it flags.
  • It's polled, not instant: replies come on your plan's schedule interval.
  • It answers only from your FAQ; anything else goes to moderators.
  • It watches one channel per setup and doesn't read images or files.

Availability and plans

Available

Its workflow is built and tested, and every app it needs is live. You can get it and set it up now.

Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.

Before you start

  • A paid plan: agents run live, and the Free plan only runs Dry Runs.
  • An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
  • These apps, connected in Settings → Integrations: Discord.
  • The app it watches, connected in Settings → Integrations (the agent starts from an app event).
  • About 15 minutes.

Set it up step by step

Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.

1. Connect your AI provider

The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.

2. Connect Discord

Connect your Discord bot (Settings → Integrations → Discord) and invite it to your server with Read Messages, Send Messages, Create Public Threads and Send Messages in Threads.

3. Pick the server and channel

Open the trigger, pick your bot, the server and the channel to watch.

SettingWhat to enterIn step
Discord bot (messages)Your Discord bot's connection; the bot must be in the server and able to read the channel. Pick your connected Discord account.“New message in the channel”
ServerThe Discord server to watch.“New message in the channel”
Channel to watchThe channel members ask questions in, e.g. #help.“New message in the channel”

4. Paste your FAQ and rules

Open “Sort the message” and replace the placeholder with your FAQ and server rules.

SettingWhat to enterIn step
Your FAQ and server rulesReplace the placeholder with your FAQ (questions and answers, links the bot may share) and your server rules. Answers only use what's written here. It starts as “[PASTE YOUR COMMUNITY FAQ HERE (QUESTIONS AND ANSWERS, LINKS YOU MAY SHARE) AND YOUR SERVER RULES]” until you replace it.“Sort the message”

5. Pick the bot and server in each step

Open “Start a thread on the question”, “Answer in the thread” and “Flag it to moderators”, pick the bot and server in each, and the moderators' channel.

SettingWhat to enterIn step
Discord bot (threads)The same bot; it needs the Create Public Threads permission. Pick your connected Discord account.“Start a thread on the question”
Server (threads)The same server.“Start a thread on the question”
Discord bot (answers)The same bot; it needs Send Messages in Threads. Pick your connected Discord account.“Answer in the thread”
Server (answers)The same server.“Answer in the thread”
Discord bot (moderators)The same bot; it must be able to post in the moderators' channel. Pick your connected Discord account.“Flag it to moderators”
Server (moderators)The same server.“Flag it to moderators”
Moderators' channelYour private moderators' channel, e.g. #mod-queue.“Flag it to moderators”

6. Test it with Dry Run

Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.

7. Switch the trigger on

Open the trigger and click “Activate app trigger”: new messages are checked on your plan's schedule interval.

How it works

The agent is a normal workflow with 9 steps (1 AI step). You can open, edit and monitor it like any other workflow.

  • New message in the channel — Starts on “New message in channel” in Discord (an app event). Starts a run for each new message in the Discord channel you pick (checked on your plan's schedule interval).
  • Sort the message — AI step (runs on your AI provider key). AI sorts the message (question, bug report, rule break or spam, chatter), answers questions from your FAQ only and writes the note for moderators.
  • What to do? — Decision: picks the branch to follow. Chatter is left alone; answerable questions get a reply in a thread; everything else goes to the moderators' channel.
  • Left alone — Kept in the run history. Branch: Leave it. The run history keeps the classification.
  • Start a thread on the question — Discord: Start a thread on a message. Branch: Answer. Starts a public thread from the member's message.
  • Answer in the thread — Discord: Send a message. Posts the FAQ answer in the new thread as your bot.
  • Answered — Kept in the run history. The run history keeps the question and the answer.
  • Flag it to moderators — Discord: Send a message. Branch: Flag. Posts the message, why it was flagged and a link to it in your private moderators' channel.
  • Flagged — Kept in the run history. A moderator decides what to do.

Test it with Dry Run

Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live. The sample has the same shape as a real event from the app.

Sample data fields

content, id, channel_id, timestamp, author_id, author_username, author_is_bot, attachments (a list), type.

  • Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.

Go live

  • Open the trigger and click “Activate app trigger”: new messages are checked on your plan's schedule interval.
  • Activating the app trigger needs the trigger's connected account. The first check only remembers what's already there, so older items don't start runs; the same item never starts two runs.
  • The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
  • When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.

Questions

Does it reply instantly?

No. Discord messages are checked on your plan's schedule interval (Discord only pushes messages over a live connection, which Fluxo Flow doesn't hold).

Can it remove spam?

No. It flags spam and rule breaks to your moderators' channel; moderators act. It never deletes, mutes or bans.

Troubleshooting

  • “No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
  • A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
  • An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
  • No runs start: activate the app trigger with a connected account. Only items created after activation start runs.
  • A step failed: open the run in History and check that step in the Trace tab for the error and what it received.

Generated from the agent's own workflow, so it always matches what the agent does. Last updated .