Integrations
Stream WhatsApp messages, conversation outcomes, campaign deliveries, and bot events to your own systems in real time. Configurable URLs, signed payloads, retry-on-failure, full audit trail.
Event types
Every action covered
Delivery
From event to your URL
On failure
Exp. backoff, 7 attempts
Payloads
HMAC-SHA256
Register N webhook URLs, each subscribed to a different subset of events. Route inbound messages to one URL, campaign analytics to another.
Pick exactly which events fire to each URL. Subscribe to message.received, campaign.completed, bot.handed_over, etc. — granular control.
Every payload signed with HMAC-SHA256 using your webhook secret. Verify on your end to confirm requests genuinely came from Edesy.
Failed deliveries retry up to 7 times with exponential backoff (30s, 2min, 10min, 1h, 4h, 12h, 24h). No data lost on transient outages.
Add custom headers per endpoint (Authorization tokens, API keys, request IDs). Headers stored encrypted in our credential vault.
Every webhook attempt logged: URL, payload, response, timing. Search by event ID, replay failed deliveries, inspect any historical request.
Customer sends a WhatsApp message, bot completes a conversation, campaign finishes delivery — any of 30+ event types fires.
Within ~100ms, the event is queued for delivery to every subscribed webhook URL. Queueing happens off the hot path so it never slows down user-facing operations.
JSON payload sent with a signed Edesy-Signature header. Your endpoint validates the signature (HMAC-SHA256 using your shared secret) and processes the event.
A 2xx response marks delivery successful. Anything else (4xx, 5xx, timeout) triggers automatic retry with exponential backoff up to 7 times.
Every attempt — including the full payload, response code, and timing — is logged in your webhook history. Useful for debugging or replaying events.
| Feature | Edesy | Typical platform |
|---|---|---|
| Real-time webhooks | Polling required | |
| Number of event types | 30+ | 5–10 |
| Signed payloads (HMAC) | ||
| Custom headers per endpoint | Hardcoded | |
| Automatic retry with backoff | Manual | |
| Delivery audit log | Limited | |
| Multiple endpoints per workspace | Single | |
| Event filtering |
Push every captured lead to your in-house CRM. Webhook fires on bot completion; your CRM creates a contact + opportunity automatically.
Zero manual data entry; leads appear in CRM within seconds
Webhook on every incoming message fires fraud-detection rules in your system. Block bad actors before they engage the bot.
Blocked 99.2% of bot-abuse attempts at scale
Push every conversation event into your data warehouse via Segment/Kafka. Run cohort analyses, churn predictions, lifetime value models.
Custom dashboards updated within 30s of WhatsApp events
On 'bot.handed_over', webhook pushes context into your help-desk tool (Intercom, Zendesk). Agent sees full WhatsApp history when they take over.
Avg handover handoff time down from 4 min to <30 sec
On high-priority events (urgent customer message, complaint detected), webhook fires Slack/Email/PagerDuty alerts to the right team.
Escalation response time SLA: 100% within 5 min
Webhook on 'order.placed' kicks off your fulfillment system. Webhook on 'review.received' updates your e-commerce site display.
End-to-end automation across 6 internal systems
Webhooks are the connective tissue of any modern SaaS platform. Without them, you're stuck either polling APIs (slow, expensive, brittle) or manually exporting data (defeats the purpose of having a 'real-time' platform). With them, you can wire Edesy into your existing systems with surgical precision — pushing exactly the events you care about to exactly the endpoints that handle them.
The events Edesy fires cover every meaningful action: incoming WhatsApp messages, outgoing message delivery status, conversation lifecycle (started, completed, abandoned, handed over), campaign progress, contact updates, opt-in/opt-out, and bot-specific events like tool calls and knowledge base retrievals. For each event, you get a JSON payload with the full context — not just an ID you have to look up via API, but the actual data your downstream system needs.
The signed-payload design is what makes Edesy webhooks safe to expose. Every POST includes an Edesy-Signature header computed as HMAC-SHA256 over the payload using a secret only you and Edesy know. Your endpoint verifies the signature before trusting the data — preventing replay attacks, forged events from competitors who guess your URL, and various other classes of webhook abuse. Most platforms skip this step; Edesy enforces it by default.
The retry-with-backoff behavior is the other quietly-important detail. Real-world webhook endpoints fail constantly — your server reboots, your database lock contention spikes, your firewall throws transient 503s. Webhooks that don't retry just lose data. Edesy retries up to 7 times over 24 hours with exponential spacing, so a temporary outage doesn't cost you events. After retries are exhausted, the event lands in a dead-letter queue you can manually replay.
Free workspace, register your webhook URL, choose events. Most teams have working webhooks in under 30 minutes.