by langgenius · v0.0.1
Discord Webhook Events trigger for receiving signed app events over HTTP.
This community listing does not yet include every recommended support, privacy, pricing, and permission disclosure. Review the available package permissions before installing.
Available inside your emploidai workspace after installation.
Available inside your emploidai workspace after installation.
Discord Webhook Events are outgoing webhooks sent by Discord when selected events happen for your application. This trigger receives those signed HTTP events and starts Dify workflows with a normalized payload.
This is different from Discord Incoming Webhooks, which are used to send messages into a channel. The Discord tool under tools/discord handles message sending; this trigger handles events coming from Discord.
Open the Discord Developer Portal, then create or select your application.
In your application's General Information page, copy the Public Key. Paste it into the trigger's Application Public Key field in Dify.
The trigger uses this key to verify the X-Signature-Ed25519 and X-Signature-Timestamp headers Discord sends with every Webhook Event request.
In Dify, create a Discord trigger subscription and select the Discord Webhook Event types you want to receive. Leave the event type list empty to accept all Discord Webhook Events.
Copy the endpoint URL that Dify provides for the trigger subscription.
In the Discord Developer Portal, open your application's Webhooks page.
Paste the Dify endpoint URL into the Endpoint URL field, enable Events, then select the same event types you configured in Dify.
Discord validates the URL by sending a signed PING payload. This trigger responds with HTTP 204 and an empty body, as required by Discord Webhook Events.
The trigger emits a single event named webhook_event.
Workflow variables include:
versionapplication_idwebhook_typeevent_typetimestampdataraw_payloaduser_id, guild_id, entitlement_id, lobby_id, and message_id when Discord includes themAPPLICATION_AUTHORIZEDAPPLICATION_DEAUTHORIZEDENTITLEMENT_CREATEENTITLEMENT_UPDATEENTITLEMENT_DELETEQUEST_USER_ENROLLMENTLOBBY_MESSAGE_CREATELOBBY_MESSAGE_UPDATELOBBY_MESSAGE_DELETEGAME_DIRECT_MESSAGE_CREATEGAME_DIRECT_MESSAGE_UPDATEGAME_DIRECT_MESSAGE_DELETEDiscord Webhook Events are not Gateway events. They do not provide the full set of Discord message and guild events. For ordinary channel message listening, Discord requires a Gateway connection with a bot token and intents, which is intentionally out of scope for this trigger.