Webhooks

Webhooks allow you to receive conversations and associated data into your systems easily without having to setup native integrations.

Setting up webhooks

• Click on the Integrations tab in RepX dashboard.
• Paste in the webhook which needs to be hit, here.
• 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. The payload is described below.

The RepX conversation completed event

The repx_conversation_completed event fires once for every conversation, as soon as that conversation is complete and RepX has finished processing it. There is one event per conversation - it isn't fired again if the same visitor returns and starts a new conversation, that produces its own event.

What the event contains

Field	Data Type	Description
id	String	Unique identifier for the conversation
event	String	Always repx_conversation_completed
transcript	String	The full conversation, message by message, including whether it happened in text or voice mode
conversation_summary	String	A short AI-generated summary of what the conversation covered
topics	Array	The topics discussed during the conversation
intent_level	String	Buying intent calculated for the conversation - high, medium or low
extracted_variables	Object	All conversation signals extracted from the conversation - both default and custom
duration	Number	Length of the conversation, in seconds
message_count	Number	Number of messages exchanged in the conversation
started_at	String	Timestamp of when the conversation began, in ISO 8601
completed_at	String	Timestamp of when the conversation completed, in ISO 8601
cta_opened	String	The CTA URL the visitor clicked during the conversation, if any
lead	Object	Lead details - id, email, first_name, last_name, lead_source, client_source and client_tracking_id
buyer_reveal	Object	Company details resolved from the visitor's IP or email - name, domain, revenue range, employee range and a confidence score
location	Object	The visitor's country, city and state

extracted_variables always contains the four default signals - email, visitor_name, phone_number and qualified. See Conversation signals for how to set them up.

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": "[e-mail]",
    "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": "[e-mail]",
    "visitor_name": "John Doe",
    "phone_number": "[phone]",
    "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: [e-mail]\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 page.