Zoho CRM + Claude
How to connect Zoho CRM to Claude
Read CRM records with Claude and Agent200. Prepare a sales briefing using the connected user’s own Zoho CRM account.
On this page
Overview
Read one selected CRM record before asking for broader context. Use the answer to prepare for a conversation, and compare its claims with the original record. Keep facts separate from Claude’s suggestions.
Start with one identified CRM record. Preserve the returned details, report missing information and keep the workflow read-only.
References: Claude documentation and Zoho CRM provider reference.
- Connector
- Zoho CRM
- Works with
- Claude · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 4 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Zoho CRM enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Zoho CRM account. They approve access once, on Zoho CRM's own page.
- Claude, with custom MCP servers allowed. Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.
Connect Zoho CRM to Claude
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers Zoho CRM and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open Connectors in Claude
On a Free, Pro, Max or Ultra plan, go to Customize > Connectors. On Team or Enterprise, an Owner goes to Organization settings > Connectors; members then find the connector under Customize > Connectors.
-
3
Step 3: Add a custom connector
Select Add, then Add custom connector. Enter a name, Agent200, and the remote MCP server URL, then choose Continue.
-
4
Step 4: Send your key as a request header
Under Authentication choose No sign-in. Open Request headers, pick
authorization, enterBearerfollowed by a space and your key, mark it Required and choose Add. Claude sends the value exactly as typed.Add custom connectorMCP: Claude custom connector (URL and request header) Remote MCP server URL: https://api.agent200.com/mcp/ Authentication: No sign-in Request header name: authorization Value: Bearer YOUR_AGENT200_API_KEY -
5
Step 5: Turn it on in a chat
In a chat, select + > Connectors and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.
-
6
Step 6: Connect your Zoho CRM account
The first time you ask Claude for something in Zoho CRM, Agent200 returns an authorization link. Open it and approve access on Zoho CRM's own page. Agent200 stores the connection and keeps it working; your password never reaches Claude or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Read the Zoho CRM deal I identify in the specified module and prepare a sales handoff from the returned fields. Include its owner, stage and relevant dates when available. Ask me to resolve missing or ambiguous identifiers. Do not change the record.
What should come back
- The selected CRM record is identified clearly.
- The answer includes only returned record identity, owner, stage and relevant dates.
- Missing information and access failures are reported; no source data is changed.
Confirm the selected organization, module and record ID. Check the fields and scopes available to the connected user. Distinguish a failed read from an empty record.
Get your API key
Create a key in the Agent200 dashboard. It reaches Zoho CRM and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Zoho CRM to Claude.
Goal: connect Zoho CRM to Claude with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/zoho-crm/framework/claude/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Zoho CRM is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Claude: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude's exact menus or commands. 4. The first Zoho CRM request returns an authorization link if the user has not connected Zoho CRM yet: show it to them and continue once they have approved access on Zoho CRM's own page. 5. Check it works with this request: "Read the Zoho CRM deal I identify in the specified module and prepare a sales handoff from the returned fields. Include its owner, stage and relevant dates when available. Ask me to resolve missing or ambiguous identifiers. Do not change the record." What should come back: - The selected CRM record is identified clearly. - The answer includes only returned record identity, owner, stage and relevant dates. - Missing information and access failures are reported; no source data is changed. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Zoho CRM, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/zoho-crm/framework/claude.md
Zoho CRM tools Claude can call
-
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.
How it works
-
01
You ask Claude
In your own words, for something in Zoho CRM.
-
02
Claude picks a tool
It sees the Zoho CRM tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Zoho CRM connection, within the tools and scopes your project allows.
-
04
Claude answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Zoho CRM account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Zoho CRM enforces what its API grants.
Troubleshooting
The source cannot be read
Confirm the selected organization, module and record ID. Check the fields and scopes available to the connected user. Distinguish a failed read from an empty record.
The answer claims more than the tool returned
Compare the answer with the retrieved data. Limit conclusions to the selected source and result scope, and say what was unavailable.
FAQ
How do I keep a deal briefing grounded?
Name the selected record and preserve the returned stage, owner and date meanings. Label absent information and separate next-step suggestions from CRM facts.
What should I compare in the first Claude answer?
Check the selected CRM record and the returned record identity, owner, stage and relevant dates. Ask Claude to label suggestions separately from source facts.
