CRM and sales
Zoho CRM for AI agents.
Prepare a clearer sales handoff.
Find CRM records and read contact, account and deal context through each user’s Zoho CRM connection. Prepare grounded sales briefings and handoffs.
About Zoho CRM
With the Zoho CRM connector, your agent reads records in each user’s own Zoho CRM account. It can search for a record, read a contact, account or deal, and follow the records related to it, using only the tools your project allows.
Zoho CRM is a customer relationship management platform for sales teams.
Tools
What your agent can do in Zoho CRM.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Zoho CRM connection.
-
Search records
Readzoho_crm_search_recordsFind matching records within the CRM module selected for the request.
-
Read a record
Readzoho_crm_get_recordRead one identified contact, account, lead or deal from its module.
-
List records
Readzoho_crm_list_recordsRetrieve records from a selected module with an explicit field and result scope.
-
Read related records
Readzoho_crm_get_related_recordsRead an available related list for a selected CRM record, such as associated notes.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Zoho CRM, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent search and read records, and switch off
zoho_crm_get_related_recordsif it should not follow links from one record to others. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example reading contacts and deals but not other modules. A call outside them is refused.
Get started
Connect Zoho CRM
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Zoho CRM
Each end user authorizes their own Zoho CRM account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Zoho CRM account, once. const connection = await agent200 .user("user_123") .connect("zoho_crm"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Zoho CRM tools
Name the user, the model and the tools. The model decides which Zoho CRM tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Find the Acme account and summarize its open deals", tools: ["zoho_crm"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Authorize the intended CRM organization
Have the end user connect Zoho CRM through managed OAuth. Confirm the organization and environment selected during authorization before requesting customer or deal data.
-
Match access to the requested module
Zoho CRM distinguishes module permissions and operation scopes. A read workflow needs access to the chosen module; a search may need additional search permission. The connected user’s CRM permissions still apply.
-
Keep the user context attached
Use the authenticated application user’s stable identity for connection and subsequent requests. Keep the Agent200 key in server configuration or a secure credential store.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Zoho CRM connector and how to use it.
Connector: Zoho CRM, through Agent200. In code: "zoho_crm". What it does: Find CRM records and read contact, account and deal context through each user’s Zoho CRM connection. Prepare grounded sales briefings and handoffs. Page: https://www.agent200.com/connectors/zoho-crm/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Zoho CRM's own page, through the authorization link Agent200 returns. Never ask a user for a Zoho CRM password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: zoho_crm_search_records, zoho_crm_get_record, zoho_crm_list_records, zoho_crm_get_related_records. Name "zoho_crm" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/zoho-crm/framework/claude/ https://www.agent200.com/connectors/zoho-crm/framework/chatgpt/ https://www.agent200.com/connectors/zoho-crm/framework/claude-code/ https://www.agent200.com/connectors/zoho-crm/framework/muse/ https://www.agent200.com/connectors/zoho-crm/framework/grok-bot/ https://www.agent200.com/connectors/zoho-crm/framework/openai-dots/ https://www.agent200.com/connectors/zoho-crm/framework/claude-duet/ https://www.agent200.com/connectors/zoho-crm/framework/hermes-agent/ https://www.agent200.com/connectors/zoho-crm/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/zoho-crm.md
Guides
Use Zoho CRM with the AI you build on.
Step-by-step setup for Zoho CRM with a specific model, assistant or agent framework.
-
Zoho CRM + Claude
How to connect Zoho CRM to Claude
-
Zoho CRM + ChatGPT
How to connect Zoho CRM to ChatGPT
-
Zoho CRM + Claude Code
How to connect Zoho CRM to Claude Code
-
Zoho CRM + Muse
How to connect Zoho CRM to Muse
-
Zoho CRM + Grok Bot
How to connect Zoho CRM to Grok Bot
-
Zoho CRM + OpenAI Dots
How to connect Zoho CRM to OpenAI Dots
-
Zoho CRM + Claude Duet
How to connect Zoho CRM to Claude Duet
-
Zoho CRM + Hermes Agent
How to connect Zoho CRM to Hermes Agent
-
Zoho CRM + OpenClaw
How to connect Zoho CRM to OpenClaw
FAQ
Zoho CRM and Agent200, answered.
Which record should the agent read first?
Start with a known module and record ID. For a deal briefing, select the deal deliberately rather than guessing from its name. Ask for clarification when several records match. See Zoho CRM’s record reference.
How should my agent handle search matches?
Treat search as candidate discovery. Compare returned identifiers and relevant fields before selecting a record; a matching name alone is not proof of identity. Do not silently combine different people or organizations. See Zoho CRM search behavior.
Can I use custom fields and modules?
Use the API names and fields supplied by the actual organization and runtime. Do not derive an API name from a display label or assume every account shares the same schema. Request only the fields needed for the answer and state when information was not returned.
Does one record contain all its related context?
A record read and a related-list read are separate operations. Request the relevant related list when needed and state what was actually retrieved. An absent relationship in the first response does not establish that none exists. See related records.
How do I keep the briefing read-only?
Enable only the read operations needed for the request. These catalogue entries do not create records, update a deal stage or write notes. Your application controls what happens after the briefing; a suggested next step is not an executed CRM change.
What permissions and implementation details should I check?
Confirm the CRM organization, module access and authorized scopes. Read and search permissions are documented by Zoho CRM. Use the tool schema advertised by your runtime for the actual call. The site’s SDK examples are conceptual; catalogue names do not define argument or response schemas.
What makes a useful sales briefing?
State which record you read, summarize the returned owner, stage and relevant dates, and separate recorded facts from questions for the team. Preserve currency and date context. Do not turn a missing field into a made-up forecast or treat a page of records as the complete pipeline.