Discord support

Last updated date:

Connect, reconnect, and troubleshoot Discord without sharing credentials or customer content through support channels.

1. Before you start

  • Create or select a Discord application and reset the bot token through the Developer Portal.
  • Enable Message Content and Server Members privileged intents as applicable.
  • Generate a bot installation URL with View Channels and Read Message History only, then install it in the exact server.
  • Do not send Discord credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Discord bot authorizationDiscord's bot authorization-flow documentation.

2. Connect Discord

  1. In Seedling, open Connections and choose Discord.
  2. Connect from workspace scope as a current Seedling workspace administrator.
  3. Enter the bot token and server ID and label; Seedling always calls the Discord API v10.
  4. Seedling verifies the bot identity and target server and stages channel overwrites, roles, and memberships without treating them as a complete read-time ACL.
  5. Allow the first Discord synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

Discord bot token rejected
Confirm the discord bot token is active, was entered without surrounding whitespace, and belongs to the intended Discord account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden Discord population as empty.
Wrong account or scope
Disconnect before retrying with the intended Discord identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the bot is still installed and can see the affected channel or thread.
  2. Check channel permission overwrites, role membership, archived threads, Message Content Intent, and Server Members Intent.
  3. Confirm the server ID still matches the exact connection; do not reconnect by server display name alone.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement discord bot token for the same Discord account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old discord bot token in Discord.