Index the messages in Discord forum channels, threads and text channels.
Discord can no longer be added as a new source. This page is for Discord sources added earlier, which keep syncing.

Before you start

  • A Pro plan or higher, and permission to edit sources in the knowledge base.
  • A Discord bot token. Create an application at discord.com/developers, add a Bot and copy its token.
  • The bot invited to your server, with View Channel and Read Message History on every channel you want to index.
  • The channels to index: a channel link, or a channel ID. To copy an ID, turn on Settings → Advanced → Developer Mode in Discord, then right-click the channel and choose Copy Channel ID.

Set up

1

Choose Discord

Open your knowledge base, go to Sources, click Add source and choose Discord. Give the source a name.
2

Connect

Paste the Bot token and the Channels, comma-separated. Channel links and IDs both work.
3

Test and add

Click Test connection. Kelu checks that the bot can read every channel you listed. Then click Add source. The first sync starts right away.

Options

The add form shows the bot token and the first four options below. The rest are on the source’s Configuration tab after you add it.
OptionDefaultWhat it does
Channels—Required. A forum channel, text channel or thread, as a link or an ID. One per line when you edit.
Server IDEmptyFallback for building citation links. Rarely needed: a channel link already carries it.
Forum posts archived within180 daysOnly forum posts archived in this window. Counted from when a post was archived, not opened. Active posts are always included. On the Configuration tab, -1 reads the whole forum.
Replace author names with pseudonymsOnWrites “Community member 1”, “Community member 2” instead of usernames. Trusted users keep their names.
Messages per channel2000Text channels only. Newest messages first. Maximum 10,000.
Only posts taggedEmptyForum tags to keep, by name or ID, one per line. For example solved. Empty keeps every post.
Skip posts taggedEmptyForum tags to drop, one per line. Wins over Only posts tagged.
Trusted usersEmptyUsernames or user IDs, one per line. Their replies are marked “Answer from …”.
Only posts a trusted user answeredOffDrops every post no trusted user replied to. Ignored while Trusted users is empty.
Exclude usersEmptyUsernames or user IDs whose messages are skipped.

What gets indexed

You nameKelu creates
A forum or media channelOne document per post: the opening message, then each reply under a heading with its author and date.
A threadOne document for that thread.
A text channelOne document with the newest messages, split into conversations. Each part links back to Discord.
  • Messages from bots and webhooks are skipped, as are empty messages.
  • A post or thread is read up to 300 messages.
  • A post’s forum tags are included in the text.
  • Each document cites its Discord link.

Sync

Discord re-syncs every 2 hours. Click Sync Now on the source page to sync right away.

Troubleshooting

  • Test connection says 401. Discord rejected the bot token. Copy it again from the Bot page.
  • Test connection says 403. The bot cannot read that channel. Give it View Channel and Read Message History there.
  • Test connection says 404. The channel ID is wrong, or the bot is not in that server.
  • Only one forum post was indexed. You named a post, not the forum. Use the forum channel’s link or ID.
  • A post is missing. Open the source’s Sync history tab. Skipped posts are listed with the reason, for example a tag filter or no trusted answer.
  • Community answers outrank your docs. Put the Discord source in its own source group, then scope public surfaces away from it.