Provider integrations

Connect Discord to FastHook

Install the FastHook Discord App in a server and route Discord events to any Destination. Choose Any Discord Event, combine several types in one Custom Discord Events Source, or select one focused event.

Discord delivers most server activity through its persistent Gateway rather than ordinary HTTP webhooks. FastHook manages the Gateway connection, heartbeat, reconnect, resume, sharding, signed Webhook Events, durable payload storage, deduplication, and downstream retries.

Create a Discord Provider Source

  1. Open Sources → New source → Provider app → Discord.
  2. Choose Any Events, Custom Events, or one of 91 event types.
  3. Select Connect new Discord server, choose a server, and approve the bot installation.
  4. Optionally filter locally by channel IDs, user IDs, role IDs, or bot authors.

Connect Discord to FastHook →

Supported events

  • Messages, edits, deletes, reactions, polls, typing, threads, pins, and channel changes.
  • Members, roles, bans, invites, presences, integrations, webhooks, and audit-log entries.
  • Voice state and server changes, stages, scheduled events, soundboard, and AutoMod.
  • Interactions, entitlements, subscriptions, application authorization, lobbies, and game direct messages.
  • Any and Custom Sources remain forward-compatible with future guild-attributable event types.

Tenant isolation

Every Provider account represents one Discord server. Gateway dispatches are routed by Discordguild_id; events without a server identity are acknowledged but never assigned to an arbitrary customer. Direct-message intents are intentionally excluded because one shared app cannot safely attribute a DM to one server installation.

Reliability and security

  • Gateway sequence and session state are persisted so disconnects resume without replay gaps.
  • Shards are created from Discord's recommended plan and respect Identify concurrency buckets.
  • Webhook Events are verified with Discord Ed25519 signatures over the exact raw request.
  • Payloads are durably stored before processing and deterministic IDs suppress provider retries.
  • OAuth credentials are encrypted at rest; revoking an account removes the bot from that server.

Permissions and privileged intents

The installation requests read-oriented server permissions needed to observe the full catalog. Member, presence, and message-content payloads use Discord's privileged intents. Large verified apps may need Discord approval before those privileged events are available at scale.

Support, privacy, and terms