Webhooks
Webhooks are available starting from the Starter plan.
You can send demo alerts to the Webhook URL.
How to Set Up Webhooks inside Alerts
Go to Settings → Alerts
Click "Create first Alert"
Toggle on Webhooks

Paste your Webhook URL — this is the URL where you want to receive webhook events
Add Custom headers if needed. Custom headers let you attach extra key-value pairs to every webhook request — useful for passing authentication tokens, routing identifiers, or any metadata your receiving endpoint expects. Click "+ Add header" to add one
Use Test webhook to confirm everything is working, then hit Save
How do I verify the webhook signature?
To ensure that webhook requests are coming from Storylane and have not been tampered with, we recommend verifying the signature included in the request headers.
Every webhook request includes an x-storylane-signature header. This signature is an HMAC-SHA256 hash of the raw request body, generated using your Webhook Verification Secret and then Base64 encoded.
1. Verification Logic
To verify the signature:
Retrieve the
x-storylane-signatureheader from the request.Get the raw body of the request (unparsed string).
Compute the HMAC-SHA256 hash of the raw body using your Verification Secret as the key.
Base64 encode the resulting hash.
Compare your generated string with the value in the
x-storylane-signatureheader.
2. Implementation Examples
Node.js (Express)
When using Express, ensure you use the raw body for the HMAC calculation.
Ruby
Python (Flask)
Webhook Example
To help you understand what kind of data you can expect from our webhooks, here's a sample response payload for unknown and known demo sessions.
Known demo sessions (known lead data)
Unknown demo sessions (unknown lead data)
Last updated
Was this helpful?