Webhook events not firing or not received
If your webhook endpoint is not receiving events from WarmySender:
- Check webhook status — Go to Settings > Webhooks and verify your webhook is active (not paused). Check the delivery history for any failed deliveries.
2) Verify endpoint URL — Make sure your webhook URL is:
- Publicly accessible (not localhost or behind a firewall)
- Using HTTPS (HTTP may be blocked)
- Returning a 200 status code within 5 seconds
- Test your endpoint — Click 'Test' in webhook settings to send a test event. If the test fails, your endpoint has an issue.
- Event selection — Verify you have subscribed to the correct events. Available events: reply.received, email.bounced, email.unsubscribed, email.opened, email.clicked, prospect.suppressed, limit.hit. For example, reply.received only fires when a reply is detected in a campaign.
5) Check delivery history — Each webhook shows recent delivery attempts with status codes. Common errors:
- 404 — Your endpoint URL is wrong or the route does not exist.
- 500 — Your endpoint is throwing an error. Check your server logs.
- Timeout — Your endpoint took more than 5 seconds to respond. Return 200 immediately and process asynchronously.
- Connection refused — Your server is down or not accepting connections.
- Retry policy — Failed deliveries are retried up to 10 times with exponential backoff (1min to 72hrs). Events are not lost on first failure.
- Signature verification — Verify using the X-Warmy-Signature header with your webhook secret (HMAC-SHA256). Format: t=timestamp,v1=signature.
- Firewall/network — Ensure your server's firewall allows incoming POST requests from WarmySender's servers.
For testing without a live endpoint, use services like webhook.site or requestbin.com to create a temporary endpoint and verify events are being sent.