A webhook is a way for an app to send other applications real-time information. A webhook will deliver data to other applications - in real time - meaning you get the data immediately. An example of a simple webhook is an 'outgoing webhook'. Outgoing webhooks will send an HTTP POST request to your specified URL.
- When a buyer is converted on TrackDrive - you can send a notification in real-time to your Slack channel with call data.
- When a buyer is converted on TrackDrive - you can send a notification in-realtime to your CRM with call data.
30+ Webhook Trigger Types
TrackDrive supports over 30 webhook triggers organized by category, giving you fine-grained control over when data is sent to your systems:
| Category | Triggers |
|---|---|
| Call Lifecycle | New call started, buyer dialled, buyer answered, call ended |
| Conversion | Buyer converted, offer converted, both converted, either converted, did not convert |
| Pre-Action | Before dial buyer, before answering call, before placing call, before sending text message, before schedule action dial |
| Data Change | Call data changed, lead data changed, contact fields changed, buyer answered with contact fields |
| Recordings | Call recording updated, call recording updated after call ended |
| Conference | Consumer/agent/buyer enter conference, consumer/agent/buyer exit conference |
| Lead | New lead created, lead opted out |
| Agent | Agent online, agent offline |
| Other | Call disposition changed, timer-based triggers |
Pre-Action Triggers: Accept or Reject
Pre-action triggers are a powerful differentiator — they fire before
an action occurs and can accept or reject it based on the webhook response.
For example, a buyer_before_dial trigger can call your external system
to verify the caller before the buyer is dialed. If the webhook returns a rejection
response, the dial is cancelled and the next buyer is tried.
- Validate leads against external systems before placing calls
- Check real-time inventory or availability before connecting
- Enforce custom business rules that live outside TrackDrive
Response Parsing
Extract data from webhook responses and store it as token values on the call or lead. TrackDrive supports three parsing methods:
- JSONPath — extract values from JSON responses using path expressions
- Regex — match patterns in response bodies using regular expressions
- XPath — extract data from XML responses using XPath queries
Parsed values are stored as tokens, making them available for routing decisions, display in reports, or use in subsequent webhooks.
Webhook Subscriptions (Simplified Webhooks)
For simpler integrations, TrackDrive also provides Webhook Subscriptions — a lightweight, Zapier-style event system. Subscribe to any of 11 event types and receive a JSON POST to your endpoint with no complex configuration:
- New Call
- Call Ringing
- Call Forwarded
- Call Ended
- Call Data Changed
- New Lead
- Lead Completed Schedule
- Lead Converted
- Lead Opted Out
- Lead Data Changed
- Incoming Text Message
Subscriptions can be filtered by offer, schedule, traffic source, buyer, telephone number, and conversion status. No request customization or response parsing is needed — just provide a URL and select your events.