Reference · built on requestConnectorMessaging & notifications

Discord

Guild channels, threads, messages, and members from Discord servers through the HTTP API and Gateway events.

Request accessPricing ↗

About

Discord runs servers, called guilds, made of text channels, forum channels, threads, and voice channels. Companies use it for customer communities, product support, and beta programs. A Discord app connects as a bot user: it calls the HTTP API at discord.com/api with an Authorization: Bot token and receives events over the Gateway, a persistent WebSocket. Message content, member lists, and presence are privileged intents that you switch on in the Developer Portal.

Through Fibric, an operator reads the channels you point it at, watches MESSAGE_CREATE and GUILD_MEMBER_ADD events, and proposes a reply, a new thread, or a webhook post for a person to approve.

This is a reference listing. It documents what Fibric would read from Discord and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Messages in a channel through GET /channels/{channel.id}/messages, 1 to 100 per call, with READ_MESSAGE_HISTORY
  • MESSAGE_CREATE, MESSAGE_REACTION_ADD, and GUILD_MEMBER_ADD events over the Gateway WebSocket
  • Message content, embeds, and attachments once the MESSAGE_CONTENT privileged intent is enabled
  • Channel objects by type: GUILD_TEXT, GUILD_FORUM, PUBLIC_THREAD, PRIVATE_THREAD, and DM
  • Pinned messages in a channel and active threads in a guild
  • Rate limit state from the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Bucket headers

Proposed actions

  • Target capability: propose a message with POST /channels/{channel.id}/messages, up to 2000 characters and 10 embeds
  • Target capability: propose a thread from a message with POST /channels/{channel.id}/messages/{message.id}/threads
  • Target capability: propose a reaction or a pin on a message
  • Target capability: propose a post through an Incoming webhook at POST /webhooks/{webhook.id}/{webhook.token}
  • Target capability: propose editing or deleting a message the bot sent

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Post a status update to a community server

    When an incident is confirmed, the operator drafts a message for your announcements channel and a follow-up when service is back. A person approves each post before it goes out.

    With Outage Notice

  • Turn help-channel threads into tickets

    Messages in a support channel that describe a product problem become a proposed ticket with the thread link attached. You approve before anything is created in your help desk.

    With Ticket Triage

  • Read what the community is saying

    Channel history is grouped into recurring themes and sudden shifts in tone. Names and message text stay inside your workspace; the operator only reports the pattern.

    With Feedback Themes, Sentiment Spike

Requirements

  • A Discord app in the Developer Portal with a bot user
  • A guild member with the right to add the bot through the OAuth2 bot scope and a permissions integer
  • The MESSAGE_CONTENT privileged intent enabled to read message text; apps in 100 or more guilds need Discord's approval for it
  • Channel permissions on the bot's role: VIEW_CHANNEL, READ_MESSAGE_HISTORY, SEND_MESSAGES, and MANAGE_WEBHOOKS where webhooks are used
Authentication
A Discord app with a bot user; every request carries Authorization: Bot and the token, and the bot joins a guild through the OAuth2 bot scope.

Limits

  • All bots share a global limit of 50 requests per second; per-route buckets return HTTP 429 with retry_after
  • A Gateway connection accepts 120 events per 60 seconds and 1,000 identifies per 24 hours across all shards
  • Apps in 2,500 or more guilds must shard; each shard carries at most 2,500 guilds
  • Requests answered 401, 403, or 429 count toward a 10,000 per 10 minute limit that ends in a temporary IP block

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Discord ↗

Questions and answers

Does Fibric need the MESSAGE_CONTENT intent?
Only to read message text, embeds, and attachments. Without it, MESSAGE_CREATE events arrive with that data omitted. You enable the intent in the Developer Portal; apps in 100 or more guilds must pass Discord's verification and be approved for it.
Can Fibric post without a bot user?
Yes, through an Incoming webhook. Discord webhooks post to a channel with a generated token and need no bot user or authentication. A guild member with MANAGE_WEBHOOKS creates one with POST /channels/{channel.id}/webhooks. The operator can only post through it, never read.
How does Discord rate limit a bot?
Globally at 50 requests per second per bot, plus per-route buckets named in the X-RateLimit-Bucket header. Exceeding one returns HTTP 429 with retry_after in seconds. Requests answered 401, 403, or 429 also count toward a 10,000 per 10 minute invalid-request limit.
Ask about Discord

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Discord through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy