> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/hubs-docs/integrations-hub/integrations/webhooks.md).
# Webhooks
Webhooks are available starting from the Starter plan.
You can send demo events to the Webhook URL.
{% hint style="warning" %}
### **Identifying Leads**
There are a few ways in which you can capture or identify leads. You can refer to the article on [Lead Tracking](/analytics-and-performance/lead-attribution.md#lead-attribution-tracking) to learn more
{% endhint %}
### **How to Integrate**
* Click the "Settings" on the left-hand menu, and then click on the "Integration" tab.
* Choose Webhook integration and click on the "Connect" button.
* Paste the webhook URL (This is the URL where you want to receive webhooks)
* Lastly, decide whether you want to send webhooks for all demo sessions (unknown and known), or only when the lead or account is known.
### 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)**
```json
{
"id": "2f37f8ce-6ecb-49a2-be12-36ae9c063042",
"buyer_reveal": {
"company_name": "Acme Inc",
"company_domain": "example.com",
"company_annual_revenue_range": "1M-10M",
"company_employee_range": "11-50"
},
"lead": {
"id": "f3694255-aed4-4514-8ce6-ac55506a67fe",
"client_source": "none",
"client_tracking_id": null,
"email": "john.doe@example.com",
"first_name": "John",
"last_name": "Doe"
},
"name": "Product Demo",
"link": "https://app.storylane.io/share/aejr8lqfghlp",
"viewed_at": "2024-05-17T10:58:05.337+00:00",
"completion": 30,
"time_spent": 125,
"checklist_completed": false,
"cta_opened": "https://example.com",
"analytics_url": "https://app.storylane.io/analytics/activity/2f37f8ce-6ecb-49a2-be12-36ae9c063042",
"utm_params": {
"gclid": "123xyz",
"utm_source": "source",
"utm_medium": "medium",
"utm_campaign": "campaign",
"utm_term": "term",
"utm_content": "content"
}
}
```
#### **Unknown demo sessions (unknown lead data)**
```json
{
"id": "2f37f8ce-6ecb-49a2-be12-36ae9c063042",
"buyer_reveal": null,
"lead": null,
"name": "Product Demo",
"link": "https://app.storylane.io/share/aejr8lqfghlp",
"viewed_at": "2024-05-17T10:58:05.337+00:00",
"completion": 30,
"time_spent": 125,
"checklist_completed": false,
"cta_opened": "https://example.com",
"analytics_url": "https://app.storylane.io/analytics/activity/2f37f8ce-6ecb-49a2-be12-36ae9c063042",
"utm_params": {
"gclid": "123xyz",
"utm_source": "source",
"utm_medium": "medium",
"utm_campaign": "campaign",
"utm_term": "term",
"utm_content": "content"
}
}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.storylane.io/hubs-docs/integrations-hub/integrations/webhooks.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
