Skip to main content

Discord

Discord support lets an agent join the channels where your team already talks. Use it when an agent should monitor a server channel, respond in context, work with shared files or images, or keep team workflows moving without everyone switching back to the web app.

The platform connects through its Discord bot. Each authorization adds exactly one server, then you choose which channels should wake this agent. The platform does not import the other servers in your Discord account.

When To Use It​

Use Discord when you want an agent to:

  • Receive messages from selected Discord channels.
  • Reply back into subscribed channels.
  • Follow team context where work is already happening.
  • Work with files, images, screenshots, and links shared in Discord.
  • Keep a Discord conversation connected to the agent timeline.
  • Coordinate across Discord, web chat, email, and other enabled channels.

If the work is private, one-off, or not tied to team chat, web chat may be simpler. Use Discord when the agent should participate in an existing server workflow.

Connect Discord​

You can start from chat. Ask the agent to connect to Discord, and it will provide the setup link.

Discord will ask you to authorize the platform and choose the server where the bot should be added.

You need Manage Server permission in the Discord server you select. After the bot is added, Discord shows that agent joined the server.

To connect another server, use Add server and complete a separate authorization. Connected servers are shared within the current personal or organization context, but each agent has its own channel subscriptions.

Return to the platform after the bot joins the server. The agent can list available channels and ask which ones should be subscribed.

Then:

  1. Open the agent that should use Discord.
  2. Ask it to connect to Discord, or open the Discord setup flow from the integration controls when available.
  3. Open the Discord setup link.
  4. In Discord, choose the server where the agent bot should be added.
  5. Continue through the Discord authorization flow.
  6. Return to the platform.
  7. Choose the server channels that should wake this agent. The agent may list available channels in chat, or you can choose them from the Discord configuration UI when available.
  8. Save the channel subscriptions.
  9. Send a small test message in a subscribed Discord channel.

Only selected channels should wake the agent. If a channel is not subscribed, do not assume the agent can see or respond to messages there.

Removing a server from the platform disables every agent subscription in that server, removes the platform-created webhooks, and uninstalls the agent bot from the server.

Choose Channels Carefully​

Subscribed channels become inbound channels for the agent. Messages in those channels can wake the agent and become part of its working context.

Good channel choices:

  • A project channel where the agent has a clear role.
  • A support triage channel where the agent summarizes or routes issues.
  • A research channel where files, links, and notes are collected.
  • A QA or engineering channel where screenshots and bug context are shared.

Avoid subscribing broad or noisy channels unless the agent really needs them. If the channel contains sensitive conversations, make sure the agent's role, connected tools, and approval boundaries are appropriate.

Give A Good Discord Request​

For Discord workflows, tell the agent:

  • Which Discord channel to use.
  • Whether it should listen, summarize, respond, or wait for direct instructions.
  • What kinds of messages matter.
  • Whether files, images, or links should be processed.
  • What should require approval before posting or taking external action.

Examples:

Watch the #support-triage channel. When customers report login problems, summarize the thread and ask me before replying.

In #bug-reports, look at screenshots and links people share. Draft a concise issue summary, but do not create tickets until I approve.

Post the weekly launch status summary in #marketing-ops after I approve the final draft.

Monitor #research-dropbox for links and files. At the end of the day, summarize anything relevant to the pricing project.

What the Platform Can Do in Discord​

In subscribed channels, an agent can:

  • Read incoming messages that wake it.
  • Reply through the agent Discord bot.
  • Use the agent's name and avatar when sending Discord messages.
  • Work with available message context, files, images, and links.
  • Attach files when replying, where supported.

Discord messages also appear in the agent timeline, so you can inspect what happened from the web app.

Safety Boundaries​

Discord is a shared communication space. Keep the agent's channel access focused.

  • Subscribe only the channels the agent needs.
  • Give clear instructions about when to reply versus summarize silently.
  • Require approval before public announcements, outreach, destructive changes, purchases, or account updates.
  • Avoid giving broad tool access to an agent that is listening to a noisy public channel.
  • Remove channel subscriptions when the workflow is finished.

Troubleshooting​

I do not see my Discord server. Make sure you are signed into the right Discord account and that you have Manage Server permission for the server.

The agent bot joined, but I do not see channels in the platform. Return to the platform and retry channel selection. The bot may need permission to list channels in the selected server.

The agent does not respond in Discord. Check that the channel is subscribed for this agent. Then ask the agent in web chat to list or confirm its active Discord subscriptions.

The agent is responding too often. Narrow the subscribed channels, revise the agent's instructions, or tell it to summarize and wait for explicit requests before replying.

The wrong channel is connected. Open Discord configuration for the agent, remove the unwanted channel subscription, and save the correct channel.

Last updated on