Automation and webhooks
CallTracker + Webhooks integration
Webhooks let you send call data anywhere — your own backend, a data warehouse loader or a no-code tool. CallTracker POSTs a JSON payload to your URL for each completed or missed call, including the full attribution captured by dynamic number insertion.
- How it connects
- Any HTTPS endpoint (Settings → CRM → Custom Webhook)
- Included in
- CallTracker Pro, no extra charge
- Best for
- Developers and data teams who want raw call and attribution data in their own systems.
What happens when a call comes in
- POSTs JSON to your URL when a call completes or is missed (configurable).
- Sends an X-Event-Type header and an X-Webhook-Secret header that is unique to your integration.
- Records the delivery result (status code, success) and shows the last error in Settings.
Data sent to Webhooks
- Call ID, caller number, duration, status and timestamp
- Recording URL and transcription text fields (usually empty, because recordings and transcripts are processed after the call ends)
- Placement ID, name and tracking number
- Attribution: traffic source, UTM parameters, gclid, fbclid, msclkid, referrer and landing page
- Workspace ID and name
How to set it up
- Open Settings → CRM and click Connect on the Custom Webhook card.
- Paste your HTTPS endpoint URL and save.
- Make a test call and confirm your endpoint receives the payload.
Limitations
- Webhooks are outbound only; there is no public REST API to query calls.
- Endpoints must be publicly reachable https:// URLs; private and internal network addresses are blocked.
- The X-Webhook-Secret value is generated automatically but is not yet displayed in the dashboard; contact support if you need it to verify requests.
- Failed deliveries are logged but not retried automatically.
Related integrations
Send your calls to Webhooks
Create a CallTracker account, add a tracking number and connect the integration from Settings.