Use webhooks to get real-time notifications when events happen in smler
Webhooks allow you to listen to real-time events. With webhooks, you can build custom integrations with your system such as:
Get a Slack notification when someone clicks you pitch deck link
Send out an email when someone clicks a link of your product
Send a lead to your sales when a potential customer clicks a link in email.
and much more....
In this guide we'll show you how to configure webhooks in smler.
Navigate to the webhooks settings page in smler
Enter your endpoint where you wish to receive the notification.
Fill in the domain and that's it done. Each time someone clicks a link. You'll start receiving a notification along with the link details. You can run your custom integration based on this action.
Make sure you hit test webhook after you have saved details to see if everything is working fine.
If you don't have an endpoint already up. You can create a temporary link using webhook.site We have a detailed guide on how to test with webhook here
Retry Behaviour
If your webhook endpoint does not respond with a success status code (2XX), we retry the request to ensure every message will be delivered.
Webhooks are retried until they are successfully delivered – with an exponential backoff to avoid overwhelming your webhook endpoint (also known as the “thundering herd problem”). The delay is capped at 24 hours from the 5th retry attempt onwards.
Retry attempt | Delay |
|---|---|
1st | 12s |
2nd | 2m 28s |
3rd | 30m 8s |
4th | 6h 7m 6s |
5th | 24h |
6th | 24h |
Temporary Disablement
If a webhook endpoint consistently fails, it will be automatically disabled after a series of failed attempts. Notifications will be sent to the Workspace owners at the following intervals:
After 5, 10, and 15 consecutive failed attempts.
On the 20th consecutive failed attempt, the webhook will be disabled.
This mechanism ensures that non-responsive endpoints do not continue to receive retry attempts indefinitely, maintaining system efficiency and preventing unnecessary load on both the sender and receiver.
You can re-enable a disabled webhook by clicking on the Enable webhook button in the webhook details page.
You can extend this integration to trigger custom flows in n8n and zapier.
Published with LeafPad