> 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/repx-chat/webhooks.md).

# Webhooks

Webhooks allow you to receive conversations and associated data into your systems as soon as conversations happen.

### **Setting up webhooks**

* Click on the **Settings > Integrations** tab in [RepX dashboard](https://app.storylane.io/repx-dashboard/integrations).
* Paste in the webhook URL that needs to receive with data about RepX conversations.
* Click **Send test webhook** to receive a test event with a sample payload from your conversations. 
* Confirm that the webhook payload is received on your end and hits the systems you expect it to hit.

RepX sends a `POST` request to the URL you configure every time a conversation completes.

#### **What the event contains**

<table><thead><tr><th width="215.234375">Field</th><th width="128.86328125">Data Type</th><th>Description</th></tr></thead><tbody><tr><td><code>id</code></td><td>String</td><td>Unique identifier for the conversation</td></tr><tr><td><code>event</code></td><td>String</td><td>Always <code>repx_conversation_completed</code></td></tr><tr><td><code>transcript</code></td><td>String</td><td>The full conversation, message by message, including whether it happened in text or voice mode</td></tr><tr><td><code>conversation_summary</code></td><td>String</td><td>A short AI-generated summary of what the conversation covered</td></tr><tr><td><code>topics</code></td><td>Array</td><td>The topics discussed during the conversation</td></tr><tr><td><code>intent_level</code></td><td>String</td><td>Buying intent calculated for the conversation - <code>high</code>, <code>medium</code> or <code>low</code></td></tr><tr><td><code>extracted_variables</code></td><td>Object</td><td>All <a href="/repx-chat/setting-up-repx/conversation-variables.md">conversation signals</a> extracted from the conversation - both default and custom</td></tr><tr><td><code>duration</code></td><td>Number</td><td>Length of the conversation, in seconds</td></tr><tr><td><code>message_count</code></td><td>Number</td><td>Number of messages exchanged in the conversation</td></tr><tr><td><code>started_at</code></td><td>String</td><td>Timestamp of when the conversation began, in ISO 8601</td></tr><tr><td><code>completed_at</code></td><td>String</td><td>Timestamp of when the conversation completed, in ISO 8601</td></tr><tr><td><code>cta_opened</code></td><td>String</td><td>The CTA URL the visitor clicked during the conversation, if any</td></tr><tr><td><code>lead</code></td><td>Object</td><td>Lead details - <code>id</code>, <code>email</code>, <code>first_name</code>, <code>last_name</code>, <code>lead_source</code>, <code>client_source</code> and <code>client_tracking_id</code></td></tr><tr><td><code>buyer_reveal</code></td><td>Object</td><td>Company details resolved from the visitor's IP or email - name, domain, revenue range, employee range and a confidence score</td></tr><tr><td><code>location</code></td><td>Object</td><td>The visitor's <code>country</code>, <code>city</code> and <code>state</code></td></tr><tr><td><code>conversation_dashboard_url</code></td><td>String</td><td>The link to the conversation in RepX dashboard</td></tr></tbody></table>

#### Sample payload:

```
{
  "id": "2f37f8ce-6ecb-49a2-be12-36ae9c063042",
  "event": "repx_conversation_completed",
  "buyer_reveal": {
    "company_name": "Acme Inc",
    "company_domain": "example.com",
    "company_annual_revenue_range": "1M-10M",
    "company_employee_range": "11-50",
    "confidence_score": "high"
  },
  "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",
    "lead_source": "Direct"
  },
  "intent_level": "high",
  "conversation_summary": "The user asked about pricing and integrations while planning a migration, and the assistant shared a calendar link to book a live demo.",
  "topics": ["Pricing", "Integrations", "Customer Onboarding"],
  "duration": 90,
  "messages_count": 3,
  "extracted_variables": {
    "email": "john.doe@example.com",
    "visitor_name": "John Doe",
    "phone_number": "+1-555-0100",
    "qualified": true
  },
  "transcript": "[text mode]\n\nAssistant: Hi, how can I help you today?\n\nUser: I want to see a demo.\n\nAssistant: Are you a new customer?\n\nUser: Yes, we're planning a migration soon.\n\nAssistant: Got it. What's your work email?\n\nUser: john.doe@example.com\n\nAssistant: Thanks, John. Pick a time on the calendar to book a live demo.",
  "started_at": "2026-07-22T10:54:05.337+00:00",
  "completed_at": "2026-07-22T10:55:35.337+00:00",
  "cta_opened": "https://example.com",
  "location": {
    "country": "United States",
    "city": "Miami",
    "state": "FL"
  }
}
```

Implementation examples in Node.js, Ruby and Python are available on the [Webhooks](https://docs.storylane.io/integrations/integrations-and-data-flow/webhooks) page.


---

# 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/repx-chat/webhooks.md?ask=<question>&goal=<user_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.