Skip to main content

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

  1. Your CRM triggers a call via the API when a lead enters a specific pipeline stage
  2. Oktivo’s AI agent makes the call and extracts structured data
  3. 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:
Store the plainToken value in your CRM’s secure credential store. It cannot be retrieved after this response.

Step 2: Configure Your CRM

Add the API token to your CRM’s HTTP integration settings:
  • Base URL: https://client-backend.oktivo.com
  • Header: Authorization: Bearer okt_your_token_here
  • Content-Type: application/json

Step 3: Trigger Calls from Your Pipeline

When a lead enters the appropriate stage, trigger a call:

Step 4: Set Up a Webhook for Results

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.

Step 5: Process Webhook Payloads

Handle incoming webhook events to update your CRM records:

Error Handling

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.

Next Steps