Skip to main content
Webhook integration
Integrating with Webhook allows you to process the raw event data from Navattic in any way you want. Navattic strives to minimize the changes to the Webhook integration, and if necessary will provide ample notice for any breaking changes. Events will be sent to your Webhook setup whenever a Visitor session in your demo is marked as closed. The timestamp in each respective event will be an ISO-8601 formatted date-time string that signifies the closing time of the session. The event will also contain information about the session, including a list of the recorded events associated with the session, as well as the corresponding end-user the session relates to, and the company account, if any (company account can be null).

Example payloads

The following examples show the structure of the session_closed payloads for visitor and account events.
Visitor event payload
Account event payload

Payload reference

There are two webhook action types, which share the same envelope but differ in what data contains:
  • Visitor event — the full session, visitor, and account details
  • Account event — the company account details only
All timestamps are ISO 8601 strings. Large numeric values (e.g. estimatedAnnualRevenue) are sent as strings.

Top-level envelope

data.session — the demo session

Fields common to all sessions: Additional fields for interactive demo sessions (type: INTERACTIVE_DEMO): Additional fields for AI agent demo sessions (type: AGENT_DEMO):

data.endUser — the visitor

data.companyAccount — the account

null on visitor events when no account could be matched (or account info is unavailable for the visitor). This object is the entire data payload for account events.

Custom property values

Each entry in endUser.customPropertyValues and companyAccount.customPropertyValues:

Recorded events

Each entry in session.recordedEvents (and mirrored in endUser.recordedEvents) is one activity event from the session:

Request headers

Testing

A free service like webhook.site can be an easy way to get started and test the Webhook integration.
Webhook.site is a public webhook testing service, so it is recommended only to send test data when using this, as you could inadvertently expose customer event data.

Opportunity owner fields

When a Launchpad presentation is connected to a Salesforce opportunity, the webhook payload includes two additional fields for the opportunity owner: These fields let you route webhook events to the right rep — for example, triggering a Slack notification or Zapier workflow that notifies the opportunity owner when their prospect views a demo.

Send data to Zapier using Webhook

Sending webhook events to Zapier allows you further filter and format the data within Zapier before sending it to additional destinations like Google Sheets, Gmail, Notion, or more. This setup demo includes all the steps you need to send data from Navattic to Zapier.
Use the Webhook integration to integrate with a Zapier workflow using a Zap URL. Learn more about triggering Zaps from webhooks.