Webhooks send real-time notifications to external systems when email events occur, letting you connect Mumara Campaigns to CRMs, analytics platforms, custom applications, and mobile alerts. You manage them under Actions → Webhooks, where each webhook has a status toggle, a Test button, and edit/delete actions.
When creating a webhook you name it, select which email events should fire it — Received, Delivered, Bounced, Rejected, Delayed, Newsletter Opened/Clicked, Transactional Opened/Clicked, and Complaints — and optionally filter by sending domain, sending node, bridge, or dedicated IP so it only fires for specific infrastructure. Then you pick a notification channel:
Web — an HTTP POST with a JSON payload is sent to your postback URL. The endpoint must be publicly accessible (HTTPS recommended) and should return a 2xx status quickly. Payloads include the event type, timestamp, recipient email, and message_id, plus event-specific fields like campaign ID, broadcast name, clicked link URL, or bounce type.
Pushover — push notifications to your mobile device using your Pushover user key and API token, with a choice of notification sounds.
Worth knowing: subscribe only to events you actually need (high-volume events like Delivered generate many requests); always use the Test button before going live; handle duplicates in your endpoint using message_id for deduplication; and your package may limit how many webhooks you can create.
