Direct integration with your own Zoho CRM org. The AI caller agent pulls Lead lists and writes call activity back; the web AI agent creates a Lead on session finalize when the chat looks like a sales conversation, complete with the full visitor context (page URL, UTM, referrer, browser). No Zapier in the middle, no field mapping — Leads land directly in your Zoho.
Two AI surfaces talk to your Zoho CRM. Both run per-workspace against your own Zoho org — your Leads stay in your Zoho, not ours.
Configurable filters (module, status, days-since-activity, max calls/hour, time window, cooldown) pull a Lead batch on a schedule. The agent calls each Lead, classifies intent, and patches the Lead with the call result and disposition.
When a website visitor's chat is classified as a sales lead, web_agent_create_lead_static creates a Zoho CRM Lead with the visitor's contact info, the chat summary, and the full request-context (page URL, referrer, UTM, IP, browser).
If a visitor submits "Email me a summary" after the session, we patch the existing Lead with the new email/phone via ZohoCRM_Update_Records rather than creating a duplicate.
You'll need a Zoho CRM admin who can register an OAuth client and generate a refresh token with CRM scopes. Setup is a one-time per-workspace task.
Visit api-console.zoho.com → Add Client → Self Client (server-to-server). Generate scopes ZohoCRM.modules.ALL and ZohoCRM.users.READ; if you want the AI Caller Agent to book meetings, also add ZohoCalendar.event.ALL. Copy the Client ID and Client Secret.
From the Self Client tab, generate a grant token with the scopes above, then exchange it for a refresh token using your token endpoint (e.g., https://accounts.zoho.com/oauth/v2/token for the .com region; use the right region endpoint for your Zoho org).
Detailed walkthrough: docs/zoho_mcp_credentials_generation.md.
Your Zoho org's connection URL is shown under Zoho's Integrations settings — typically of the shape https://mcp.zoho.com/mcp/<org-key>/sse. Copy the full URL including the org-key path segment.
Portal: Settings → Integrations → CRM Provider → Zoho CRM. Paste in the four required fields: URL, Client ID, Refresh Token, Token Endpoint. (Calendar UID is optional — only needed for the AI Caller Agent's calendar booking action.)
Make sure Active CRM Provider is set to Zoho. Save — the change takes effect immediately without a restart.
Open the AI support widget on your site, complete a chat that the LLM classifies as interested, and resolve the session. Within a few seconds a new Lead should appear in your Zoho CRM with the visitor info and request-context block in the description.
For the AI Caller Agent: enable it for a station with the Lead-list filters configured, and watch the Caller Agent dashboard for outbound calls + Lead activity updates.
Stored under your workspace's namespace. The portal writes these for you.
| Key | Purpose | Required? |
|---|---|---|
organizations.<org>.crm-provider | Active CRM routing (zoho · zapier · none) | Required |
organizations.<org>.zoho-mcp-url | Your Zoho connection URL | Required |
organizations.<org>.zoho-mcp-client-id | OAuth Client ID | Required |
organizations.<org>.zoho-mcp-refresh-token | OAuth refresh token | Required |
organizations.<org>.zoho-mcp-token-endpoint | Region-specific token endpoint | Required |
organizations.<org>.zoho-mcp-calendar-uid | Calendar UID for AI-Caller meeting bookings | Optional |
The agent UI hides the Caller Agent tab when Zoho isn't configured for this workspace, so you don't see surfaces that can't work yet.
Direct integration, no field mapping to maintain, and Leads land directly in your Zoho org. Have a play with it.