Advanced Analytica Advanced Analytica: IBOM
← All connectors
Discord logo

Source connector

Discord

Set up Discord as a source and move its data into your chosen destination.

Version 0.1.21 community alpha

Discord

Set up the Discord source connector and find its reference information on this page.

Before you start

  • A Discord account with access to the Developer Portal
  • A Discord bot token, created in Step 1 below
  • The bot must be invited to every guild (server) you want to sync

Set up the connector

Step 1: Create an application and bot

  1. Go to the Discord Developer Portal.
  2. Click New Application and give it a name.
  3. Go to the Bot section in the left sidebar.
  4. Click Reset Token to generate a bot token. Copy and store this token securely. You’ll need it to configure the connector.

:::caution Discord only shows the token once. If you lose it, you must reset it to generate another. :::

Step 2: Enable privileged intents

You must enable privileged intents for some streams:

  1. In the Developer Portal’s Bot section, scroll to Privileged Gateway Intents.
  2. Enable Message Content Intent to sync full message content, embeds, attachments, and components. Without this intent, the messages stream returns empty content, embeds, attachments, and components fields for most messages.
  3. Enable Server Members Intent to sync the members stream. Without this intent, the List Guild Members endpoint returns a 403 error.

:::note If your bot belongs to 100 or more guilds, Discord requires your application to be verified. Verified bots must request privileged intent approval through the Developer Portal before these intents take effect. :::

Step 3: Invite the bot

  1. Go to the OAuth2 section in the left sidebar.
  2. Under OAuth2 URL Generator, select the bot scope.
  3. Under Bot Permissions, select:
    • View Channels: required to read channels and messages
    • Read Message History: required to access historical messages and archived threads
    • Manage Threads: optional and only required for private archived thread messages. Channels without it are skipped.
  4. Copy the generated URL and open it in your browser.
  5. Select the guild where you want to add the bot, then click Authorize.

Repeat these steps for every guild you want to sync.

Step 4: Set up Discord in Airbyte

For Airbyte Cloud:

  1. Go to Sources and click New source.
  2. Find and select Discord.
  3. Enter a name for your source.
  4. Paste the Bot Token you copied from the Developer Portal.
  5. Click Set up source.

For Airbyte Open Source:

  1. Go to Sources and click New source.
  2. Find and select Discord.
  3. Enter a name for your source.
  4. Paste the Bot Token you copied from the Developer Portal.
  5. Click Set up source.

Supported sync modes

You can use the following sync modes with the Discord source connector:

FeatureSupported?
Full Refresh SyncYes
Incremental - Append SyncNo
NamespacesNo

Supported streams

The connector syncs data from these Discord API endpoints:

StreamDescription
guildsGuilds (servers) the bot has joined. Parent stream for all other streams.
channelsAll channels in each guild, including text, voice, category, forum, and announcement channels.
messagesMessages from text channels, announcement channels, active threads, and archived threads. Paginated newest-to-oldest.
membersGuild member list with roles, join dates, and nicknames. Requires Server Members Intent.
rolesAll roles in each guild with permissions and metadata.
threadsActive threads across all channels in each guild.
scheduled_eventsScheduled events in each guild.

Rate limits

Discord applies global and per-route rate limits:

  • Global limit: 50 requests per second
  • Per-route limits: Limits vary by endpoint and are provided through X-RateLimit-* response headers

The connector reads the Retry-After header and waits before retrying, automatically handling rate limits.

Limitations

  • Message channel coverage: The messages stream reads text channels (type 0), announcement channels (type 5), and their active and archived threads. It doesn’t directly fetch messages from forum, media, or voice channels. However, it includes active threads, including active forum posts. The active threads endpoint returns threads from every channel type.
  • Archived forum and media threads: The connector only fetches archived threads from text and announcement channels. It doesn’t include archived forum posts or archived media channel threads.
  • Message Content Intent: Without the MESSAGE_CONTENT privileged intent enabled in the Developer Portal, the messages stream returns empty content, embeds, attachments, and components fields for most messages. Messages mentioning the bot or sent in DMs with the bot still include content.
  • Server Members Intent: The members stream requires the GUILD_MEMBERS privileged intent. Without it, the List Guild Members endpoint returns a 403 error. The connector surfaces this error, so you know which intent to enable.
  • Messages pagination: The messages stream runs a full refresh, moving from newest to oldest with the before cursor parameter. The initial sync may take a long time for channels with large message histories. Incremental sync isn’t yet supported.
  • Thread messages: Messages from active and archived threads are automatically included in the messages stream with regular channel messages. Private archived threads require the bot to have Manage Threads and Read Message History permissions. The connector skips channels where the bot lacks these permissions by ignoring the 403 Missing Access response. This allows the rest of the messages stream to sync. Grant Manage Threads if you need private archived thread messages.
  • Channel permissions: The connector skips channels the bot can’t access. It ignores 403 errors for per-channel streams. Streams requiring guild-level permissions (members) fail with an actionable error when permissions are missing.

Changelog

Expand to review
VersionDatePull RequestSubject
0.1.212026-11-1091462Update dependencies
0.1.202026-11-0390519Update dependencies
0.1.192026-10-2789841Update dependencies
0.1.182026-10-2089174Update dependencies
0.1.172026-10-1388566Update dependencies
0.1.162026-10-0788179Skip channels where the bot lacks MANAGE_THREADS for private archived threads instead of failing the whole messages stream
0.1.152026-10-0687822Update dependencies
0.1.142026-09-2987112Update dependencies
0.1.132026-09-2286591Update dependencies
0.1.122026-09-1585991Update dependencies
0.1.112026-09-0885423Update dependencies
0.1.102026-08-1884518Update dependencies
0.1.92026-08-1183874Update dependencies
0.1.82026-08-0483417Update dependencies
0.1.72026-07-2882872Update dependencies
0.1.62026-07-2182364Update dependencies
0.1.52026-07-1481769Update dependencies
0.1.42026-06-3081015Update dependencies
0.1.32026-06-2380400Update dependencies
0.1.22026-06-1679820Update dependencies
0.1.12026-06-0979241Update dependencies
0.1.02026-06-0876376Initial release of source-discord connector with 7 streams: guilds, channels, messages, members, roles, threads, and scheduled_events.
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.