Skip to main content
The Discord connector integrates Tess with Discord. Once connected, the AI can help read accessible channels, summarize community discussions, and support messaging workflows inside chats and agents. Discord is part of the Tess Connectors ecosystem and uses OAuth authentication for Apps connectors.

​
Prerequisites

  • A Discord account with access to the servers/channels you need.
  • Permission to authorize the Discord app for those servers.

​
How to connect

On some Apps connectors, the OAuth consent screen may show a third-party connection bridge name rather than Tess. That is normal—review the requested permissions and continue if they match what you expect.
1

Open the Connectors panel

In chat, click the + next to the message box and select Connectors. You can also manage connectors while editing an agent in Agent Studio.
PRINT: (Connectors panel with Discord highlighted and the Connect button visible)
2

Find Discord and click Connect

Under Apps, locate Discord and click Connect to start authentication.
PRINT: (Provider authorization / consent screen for Discord)
3

Authorize access

Sign in with the account you want to use and review the requested permissions before confirming.
4

Confirm it is active

Back in Tess, Discord should appear under Connected, ready for chats and agents.
PRINT: (Tess callback or Connectors list showing Discord as Connected with a success state)

​
What you can do

  • Find channels and recent messages the account can access
  • Summarize community discussions into decisions and action items
  • Support moderation and community ops with clearer context
  • Help draft or send updates when write permissions are available
  • Keep community signal close to your Tess workflows

​
Example prompts

  1. Summarize the last day of discussion in #product-feedback and list top requests.
  2. What announcements were posted this week in the community server?
  3. Draft a release update for #announcements and show it before sending.
  4. Find messages mentioning onboarding friction and group them by theme.

​
Best practices

  • Mention the server/channel when names collide.
  • Ask for a draft before posting to public channels.
  • In agents, define whether Discord is for listening, summarization, or posting.

​
Troubleshooting

Reconnect with an account that belongs to the target server and has the needed channel permissions.
Reconnect Discord in Connectors after app removal or token revocation.
The connected account may be read-only there. Check Discord roles/permissions.
Tess uses the permissions of the connected account. It does not expand access beyond what that account can already do.Connectors involve access to external systems. Only connect accounts that fit the usage context, and review permissions carefully.