How It Works
A webhook is a way for an app to send other applications real-time information — you get the data the moment it happens. An outgoing webhook sends an HTTP POST request to a URL you specify.
- When a buyer is converted on TrackDrive, send a real-time notification to your Slack channel with call data.
- When a buyer is converted on TrackDrive, send a real-time notification to your CRM with call data.
30+ Webhook Trigger Types
TrackDrive supports over 30 webhook triggers organized by category — spanning the call lifecycle, conversions, data changes, recordings, conference events, leads, and agent status — giving you fine-grained control over when data is sent to your systems.
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 a value from a webhook response and store it as a token on the call or lead. Parsing works over JSON or XML, and the extracted value can be reused for routing decisions, reports, or 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. Subscriptions can be filtered by offer, schedule, traffic source, buyer, telephone number, and conversion status — just provide a URL and select your events.
