Discord Webhook Destination Configuration

When to use this destination type

Choose DISCORD_WEBHOOK when the receiver target is Discord execute webhook API. Destinations are outbound delivery targets: they do not decide whether a source request should be accepted, and they do not own connection filters or transformations. They own where the final delivery goes and how FastHook should authenticate, pace, disable, and inspect that delivery.

A Discord Webhook destination can be reused by multiple connections when several source branches should feed this receiver. Reuse keeps its capacity, credentials, and attempt evidence attached to one destination id.

FastHook dashboard fields

In the dashboard, create a destination, set Destination Type to DISCORD_WEBHOOK, then fill the fields below.

API config fields

The REST API stores Discord Webhook destination behavior under config. Use PATCH for focused edits and PUT only when the request contains the full config you want to keep.

{
  "name": "orders-api",
  "type": "DISCORD_WEBHOOK",
  "config": {
    "url": "https://api.example.com/webhooks/fasthook",
    "http_method": "POST",
    "auth_type": "FASTHOOK_SIGNATURE",
    "auth": {},
    "rate_limit": 10,
    "rate_limit_period": "second"
  }
}

curl -X POST "https://api.fasthook.io/v1/destinations" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "orders-api",
  "type": "DISCORD_WEBHOOK",
  "config": {
    "url": "https://api.example.com/webhooks/fasthook",
    "http_method": "POST",
    "auth_type": "FASTHOOK_SIGNATURE",
    "auth": {},
    "rate_limit": 10,
    "rate_limit_period": "second"
  }
}'

Authentication

Discord Webhook destination authentication is outbound. It helps this receiver trust or accept FastHook delivery and remains separate from source authentication for the original webhook producer.

• Discord webhook URL for channel delivery
• Original signed Interaction token for automatic follow-up delivery

HTTP methods and rate limit

Discord Webhook uses the methods below for delivery attempts. Its destination rate limit is shared by every connection that targets this receiver.

Rate limit: Locked to 1 request per second.

Delivery behavior

• WEBHOOK mode calls Discord's execute webhook endpoint with wait=true. The webhook URL is the credential; keep it secret and rotate it if exposed.
• INTERACTION_FOLLOWUP mode obtains the application ID and interaction token from the original signature-verified request. No token is stored in destination configuration.
• FastHook automatically defers ordinary interactions inside Discord's three-second deadline; follow-ups must be delivered before Discord's 15-minute token lifetime ends.
• Embeds templates must render to a JSON object or an array of embed objects.
• Forum and media channel webhooks require thread_id_template or thread_name_template. Threads, username, and avatar are not supported by Discord's follow-up endpoint.
• Components templates render to a JSON array; FastHook enables Discord's with_components query option automatically.
• Poll templates render to a Discord poll request object.
• File uploads use multipart/form-data with payload_json and files[n]. FastHook accepts up to 10 public HTTPS files, 10 MiB per file, and 20 MiB total per message; private, loopback, and metadata hosts are blocked.
• For private slash-command replies, enable Private slash-command responses on the Discord Interactions Source. FastHook sets EPHEMERAL in the initial defer so the follow-up inherits it.
• Allowed mentions default to an empty parse list so rendered @mentions do not ping recipients unexpectedly.
• Discord webhook destinations are locked to 1 request per second to avoid message bursts.

Setup checklist

1. Create a FastHook destination and choose DISCORD_WEBHOOK as the destination type.
2. Choose Channel webhook for a normal channel message, or Slash-command follow-up for the result of a routed Discord Interaction.
3. For Channel webhook, create a webhook in Discord channel settings, copy its URL, and configure a thread ID or thread name for Forum/Media channels.
4. For Slash-command follow-up, connect the destination to a Discord Interactions source; FastHook reuses the original interaction token automatically.
5. Set message text, optional embeds, components/buttons, poll, file uploads, flags, and allowed mentions policy.
6. Connect only Discord-worthy events through filters before routing to the destination.

Troubleshooting

Related docs

• Destinations
• Filter and route events
• Control throughput
• Discord execute webhook
• API reference