Webhooks
Signed guild webhooks, test delivery, bounded retries and current event fanout limits.
Event catalog
Current fanout is intentionally small: moderation case changes, completed moderation actions, safe config updates when available, and delivery lifecycle events.
Automod violation, reaction-role, scheduler completion and arbitrary custom events remain future fanout slices.
Deliveries
Webhook deliveries carry event id, guild id, event name, created timestamp and bounded safe payload data.
Delivery history and retry state stay visible without exposing signing secrets or raw exception details.
Signature verification
Each delivery is signed with HMAC-SHA256 headers.
Consumers verify timestamp plus payload using their configured endpoint signing secret.
Retries
Failed deliveries retry with exponential backoff.
After the retry budget is exhausted the delivery is marked failed and emits a failure event.
n8n
The n8n path documents a safe integration runway, not a full automation marketplace.
Use signed webhooks now and wait for scoped API key issuance before enabling write-back workflows.
signature = HMACSHA256(secret, timestamp + "." + payload)| Concept | Foundation behavior |
|---|---|
| guild.config.updated | Configuration changed for one guild. |
| moderation.case.created | A durable moderation case was created. |
| moderation.case.updated | A durable moderation case changed status or outcome. |
| webhook.delivery.failed | Delivery exhausted retry policy. |
| future events | Automod, reaction-role and scheduler fanout remain deferred. |