Overview
Verify provider callbacks, persist and deduplicate webhook events, then process delivery, inbound-message, template and provider updates asynchronously.
Problem
Providers send asynchronous delivery and inbound events that need fast acknowledgement and reliable domain processing.
Solution
Use connection-specific provider webhook receivers plus durable ProviderWebhookEvents and the provider-webhook-processing worker.
How it works
The webhook edge verifies and normalizes the event, persists it, acknowledges receipt, and leaves heavier message/conversation/provider state transitions to background processing.
Who is this for
Integration Engineer
Communications Operator
Expected outcomes
- Fast webhook acknowledgement with durable processing
- Normalized delivery, inbound-message, template and provider state
Key metrics
Security impact
- Provider webhook payloads, event identifiers, connection references, delivery and inbound-message state · PII: yes where recipients, messaging identities, message content, consent, media, or external identity mappings contain personal data
Compliance
- Provider signature verification, deduplication, connection policy, durable processing, and audit state
Availability & next steps
Starter
Team
Enterprise