Connect Discord and BeforeQuery indexes channel history and forum posts, so answers a maintainer typed once in #support are retrievable everywhere else — the widget, the API, Slack, your support form.
Separate from the Discord bot, which answers in a server. This one reads what was said there. Many teams run both.

​
Prerequisites

  • A bot token — create an application at discord.com/developers, add a Bot, copy its token.
  • The bot invited to your server with View Channel and Read Message History, and the Message Content Intent enabled on the bot’s page.
  • Channel IDs — turn on Settings → Advanced → Developer Mode, then right-click a channel and Copy Channel ID.
  • A BeforeQuery workspace owner role.

​
Set up the connector

1

Add the source

Open Knowledge Base → Sources → Add source and choose Discord. Paste the bot token and one channel ID per line.
2

Set the server ID

Right-click the server and Copy Server ID. Without it, citations can’t link back to the message.
3

Check the connection and add

Click Test connection — every channel you named is checked, not just the first. Then click Add.

​
Connection settings

​
Data ingested

Every document carries the Discord link to what it came from and the channel or post name as its title. The body depends on what you point it at: Archived forum posts are read newest-first, so the forum posts within cutoff ends the walk. Active posts are always included whatever it says.

​
Keeping content in sync

Discord re-syncs every 2 hours — there is no schedule to configure, and Sync on the source’s page runs one now if you cannot wait. Only changed content is re-embedded. See Sources Overview.

​
Troubleshooting

  • Empty messages in the index? The Message Content Intent is off — enable it in the developer portal.
  • One channel missing? The bot lacks View Channel there. Test connection names it.
  • A forum indexed nothing? Check the ID is the forum channel, not one post in it — though a post ID works too and indexes just that thread.
  • Citations that don’t link anywhere? The server ID is unset.
  • Community answers outranking the docs? Put Discord in its own source group and scope your public surfaces away from it.