End-to-end guide for integrating Oktivo with your CRM
CRM Integration Guide
This guide walks you through connecting Oktivo to your CRM so you can trigger AI voice calls from your sales pipeline and receive structured results back.
Architecture Overview
┌─────────────┐ API Token ┌──────────────────┐│ Your CRM │ ─────────────────────▶ │ Oktivo CRM API ││ │ │ ││ │ ◀───── Webhook ──────── │ Voice Agents │└─────────────┘ └──────────────────┘
Your CRM triggers a call via the API when a lead enters a specific pipeline stage
Oktivo’s AI agent makes the call and extracts structured data
Oktivo sends results back to your CRM via webhook
Step 1: Generate an API Token
Create a token from the Oktivo dashboard or via API:
Create an endpoint to receive call analysis back into your CRM. You can do the same in the dashboard under Connecter > Webhooks. Webhook requests use the login token (JWT) of a dashboard user, not the okt_ API token.
Contact is on the Do Not Disturb list, or calling is not allowed at this time
Do not retry straight away
429
Concurrent-call limit reached, or more than 60 requests in a minute
Wait, then retry with growing delays (use the Retry-After header when present)
503
Service unavailable
Retry with exponential backoff, and respect the Retry-After header when present
Using Panzo, n8n or Zapier
Panzo: follow the dedicated Panzo guide. It uses the Panzo CRM delivery format.
n8n, Zapier and similar tools: use the same steps as above. Place calls with an HTTP request to /api/v1/crm/calls, and receive results with the tool’s webhook trigger. Keep the Standard (default) delivery format. If the tool cannot check signatures, restrict access in another way, such as a secret path in the URL.