Invoca setup

What Invoca can do

Invoca has three webhook types, per their Webhooks Setup guide. Only Real-Time Routing Webhooks fire before the call is connected AND use the response to route: a RealTime node in the campaign's call treatment fires the webhook, waits up to 4 seconds, and falls back to its child node (which can be EndCall) if nothing comes back, as specified in Invoca's developer docs.

Two honest constraints. Real-Time Routing is available only in some Invoca account packages and must be enabled for your network, and the exact response format the RealTime node expects (it resolves to a call destination, not a plain verdict) is documented in Invoca's login-gated setup article. Ask your Invoca CSM for both before building. Pre-transfer webhooks are not a blocking path: Invoca's own FAQ confirms they fire only once the destination connection is established.

Screening data on any plan

Without the Real-Time Routing package you can still screen every caller for the record: a Custom Webhook POSTs the caller number to your lookup URL, and every verdict lands in your CallerSift lookup log with the reason and line type, ready for export, buyer disputes, and suppression lists.

1. In Invoca, open Integrations, then Custom Webhooks, and click New Webhook (the Heap walkthrough shows the same wizard).
2. Choose the webhook type, select POST, and paste your lookup URL.
3. Set the Content-Type to JSON and build the body with Add Substitute Parameter: the caller's number is the calling_phone_number field (see the Calls In Progress API field list). Add your api_key as a static field.
4. Set the firing conditions and save.

Gating calls with Real-Time Routing

1. Confirm with your Invoca CSM that Real-Time Routing Webhooks are in your package and enabled for your network, and get the response contract from their gated setup article (Using Real-Time Routing Webhooks, article jhdcp92865-522).
2. The shape: a RealTime node fires your webhook with the caller number; on allow the response resolves the real destination, on block it returns nothing and the 4 second fallback child (EndCall) takes the call. Your CallerSift verdict drives that decision through a thin adapter you host, since the node expects a destination rather than a verdict string.
3. Note Invoca's timing rules: 4 seconds for the routing decision, 2 seconds for returned data to populate call records, and campaign Test Call mode does not fire these webhooks; verify with a real call.

Official Invoca docs

1. Webhooks Setup: the three webhook types and management paths.
2. Call Treatments and IVR: the tree builder and node types.
3. Advertiser Campaigns API: the RealTime node, webhook_id, 4 second timeout, and fallback child.
4. Calls In Progress API: calling_phone_number and custom data fields.