Outbound events

Webhook delivery for integration workflows

Source docs describe admin-managed webhook subscriptions, delivery attempts, dead-letter handling, bounded retries, test deliveries, and notification-triggered channels.

Event selected

Admin trigger and subscription configuration determine outbound delivery.

Outbox queued

Delivery records track attempts, status, last error, and retry state.

Endpoint owner responds

Support flow separates payload questions, endpoint failures, retries, and ownership changes.

Positioning details

HTTPS-first public posture

Public pages should avoid private endpoint examples. Source docs include SSRF-related controls that require security review before deeper publication.

Operational transparency

Admin surfaces list subscriptions, delivery attempts, provider health, and outbox dead letters where implemented.

Supportable failure modes

Help content should ask for event type, delivery ID, endpoint owner, timestamp, and sanitized error symptoms.

Draft/review-needed. Do not publish customer endpoint URLs, webhook secrets, payloads with PHI, or internal retry schedules beyond public-safe summaries.