Zapier

The API adapter is implemented. Validate your own account and authorized actions before routing production calls.

Before you start

Connect the account belonging to this business and workspace. Vendor subscriptions, API limits and role permissions still apply.

API: Webhooks by Zapier Catch Hook

Authentication: Secret, encrypted Catch Hook URL

Get access and connect

1. Create a Zap, choose Webhooks by Zapier and the Catch Hook trigger.
2. Copy its HTTPS hooks.zapier.com/hooks/catch URL into the secret field; choose the Zap's downstream action and publish it.
3. Enable changes for the Verbatik connection and select Send call outcome for the desired agent or post-call automation.
4. Run an authorized call and inspect the Zap's trigger history. The connection check does not send a test event.

Account requirements

• A Zapier plan that includes Webhooks by Zapier; an enabled Zap.

Permissions

Grant the subset needed for the actions you enable. API scopes do not override the connected user’s record permissions or vendor validation rules.

Connection fields

• webhookUrl — Zapier Catch Hook URL (required). Secret fields are saved as workspace credentials.

Available actions

• send_call_outcome — Write · available for after-call automation. Send the completed call summary and outcome to the workspace's configured Zapier Catch Hook. This can start the connected Zap; send only the necessary data.

Provider-specific behavior

Test connection validates the destination configuration without posting a customer outcome. Validate delivery with an explicitly authorized sample event.

Verify before going live

Run Test connection and one read action against a known permitted record. Then test each intended write in an authorized sandbox. Check the provider’s own record and the Verbatik receipt. Publish the agent after assigning its tools. If a write has an unknown outcome, reconcile it with the vendor before trying again.

Vendor documentation

• Setup and API documentation