Discord Webhook Event Trigger icon

Discord Webhook Event Trigger

Receive Discord Application Webhook Events (e.g. APPLICATION_AUTHORIZED, ENTITLEMENT_CREATE) via HTTPS webhook with Ed25519 signature verification

Discord Webhook Event Trigger

AI-generated

Summary

Receives Discord application webhook requests at the configured n8n path, verifies their Ed25519 signatures, and emits matching type 1 events as workflow items. It answers Discord’s type 0 verification PING with HTTP 204 and acknowledges event requests with HTTP 204.

Inputs

  • Path (required) — URL slug appended to the n8n webhook base URL. Set the resulting full URL as the application’s Webhook Events Endpoint URL in Discord.
  • Event Types — Optionally select event types to forward: APPLICATION_AUTHORIZED, APPLICATION_DEAUTHORIZED, ENTITLEMENT_CREATE, LOBBY_MESSAGE_CREATE, or QUEST_USER_ENROLLMENT. Leave empty to forward every event type.
  • Additional Event Types — Optionally add event type names separated by commas or whitespace. These are combined with the selected Event Types and can include types not listed in the options.
  • Discord Interaction API credential (required) — Provide the Discord public key used to verify the request signature.

Output shape

One workflow item containing the full JSON payload for each accepted type 1 event.

Requests with invalid signatures receive HTTP 401; valid but malformed JSON receives HTTP 400. Type 0 PING requests are acknowledged with HTTP 204 and produce no item. Events excluded by the configured filters are acknowledged with HTTP 204 and produce no item.

Examples

Example 1: Receive all Discord application webhook events

Set Path to a URL slug, configure its full n8n webhook URL in Discord, provide the Discord public key credential, and leave both event filters empty.

Example 2: Receive only entitlement creation events

Select ENTITLEMENT_CREATE in Event Types; the node acknowledges other event types but does not emit them.

Links

Discussion