TrackDrive setup

How it works on TrackDrive

TrackDrive's custom webhooks fire on call events, and its response parsers pull values out of the webhook's JSON reply and store them as tokens on the call. Tokens drive routing filters, so the CallerSift pattern is: webhook on call start, parse verdict into a token, and let every buyer filter on it. TrackDrive also supports pre-action triggers that accept or reject an action from the webhook response directly.

TrackDrive's public API docs cover everything below; parts of their support center sit behind a customer login, so lean on TrackDrive support for exact dashboard walkthroughs if a screen differs.

Your lookup URL

Every workspace gets one lookup URL, shown on your dashboard home page. POST the caller number to it and the JSON response answers verdict: allow or block.

POSThttps://api.callersift.com/v1/your-workspace

Create the webhook

{
    "caller_number": "[caller_id]",
    "api_key": "fck_your_key"
}

1. Create an outgoing webhook on the trigger new_call_started, scoped to your company or offer (TrackDrive's outgoing webhooks API lists every trigger). The call-flow builder can also fire a webhook before any routing node.
2. On the webhook URL, set remote_method to post_body with the JSON body below; [caller_id] is TrackDrive's caller token (their expressions feature replaces tokens in webhook bodies and URLs).
3. Prefer the key in a header instead? Set post_headers to X-Api-Key: fck_your_key and drop api_key from the body; both work.

TrackDrive's docs show caller_id as both 10-digit and E.164 depending on account setup. Place one test call and check the number that lands in your CallerSift lookup log; if it arrives without the +1, ask TrackDrive support for the E.164 token or prefix it with an expression.

Parse the verdict and route on it

1. Add a response parser on the webhook: value_path verdict, stored as a token such as callersift_verdict, with 200 as the success code.
2. Filter every buyer (or the routing node) on callersift_verdict equals allow. A blocked caller matches nothing and never rings a buyer; TrackDrive's company-wide blacklist can hard-block repeat offenders on top.
3. Alternative: the buyer_before_dial pre-action trigger cancels the dial when the webhook rejects. It runs per buyer attempt, so one call can fire several lookups; the single call-start webhook plus a token filter is the cleaner default.

Official TrackDrive docs

1. Custom webhooks: triggers, pre-action accept/reject, response parsing.
2. Outgoing webhooks API: trigger types and scoping.
3. Webhook URLs API: methods, custom bodies, custom headers.
4. Response parsers API: value_path extraction into tokens.
5. Expressions and formulas: the [field_name] token syntax.
6. Inbound call routing: token-based buyer filters and blacklists.