Zoho CRM + Claude Code
Build a Zoho CRM reader with Claude Code
Implement a read-only flow in your application
Use Claude Code to build a Zoho CRM reader with Agent200. Validate runtime schemas and user identity, then prepare answers from returned source data.
On this page
Overview
Use Claude Code to build a CRM record reader inside your application. Supply the runtime’s actual tool definitions, then implement identifier validation, missing-field handling and an explicit path for access failures.
Start with one identified CRM record. Preserve the returned details, report missing information and keep the workflow read-only.
The Agent200 SDK examples are conceptual. Implement against the runtime’s real tool schemas and supported client interfaces; no package or argument mapping is implied.
References: Claude Code documentation and Zoho CRM provider reference.
- Connector
- Zoho CRM
- Works with
- Claude Code · Coding agent, with the SDK
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 4 tools
- Model in examples
openai/gpt-5.6-sol
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 Code in your project. It writes the code with the Agent200 SDK; you review it.
Connect Zoho CRM to Claude Code
-
1
Step 1: Create your Agent200 API key
Create a key on the API keys page. Enable the Zoho CRM read operations your task needs. Store the key securely.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
Step 2: Inspect the runtime tool definitions
Validate the identifiers and schema for the selected CRM record. Keep the authenticated application user attached to the request.
-
3
Step 3: Connect the user’s Zoho CRM account
Use the same stable user identity for authorization and later requests.
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); } -
4
Step 4: Build and test the read-only answer
Produce the sales briefing from returned facts. Handle missing context and access errors explicitly. The snippet illustrates the sequence, not an SDK installation contract.
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);
Test your connection
Run one request to check everything is wired up.
Ask
Implement a read-only Zoho CRM CRM record reader using the actual runtime tool definitions. Validate identifiers and the authenticated user, and handle missing fields and refused calls. Flag missing schemas instead of inventing SDK arguments.
What should come back
- An implementation plan tied to real runtime schemas.
- Explicit handling of missing identifiers, refused calls and absent fields.
- No invented package, tool arguments or source data.
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 Code.
Goal: connect Zoho CRM to Claude Code with Agent200. Guide: https://www.agent200.com/connectors/zoho-crm/framework/claude-code/ 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. Make sure Zoho CRM is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs. 3. Add the Agent200 SDK to the project and create a client with that key. 4. Give every request a stable id for the end user. Agent200 uses only that user's own connections. 5. Connect the user's Zoho CRM account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on Zoho CRM. 6. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "zoho_crm" in the tools. The model decides when a Zoho CRM tool is needed; Agent200 executes the call. 7. Check it works with this request: "Implement a read-only Zoho CRM CRM record reader using the actual runtime tool definitions. Validate identifiers and the authenticated user, and handle missing fields and refused calls. Flag missing schemas instead of inventing SDK arguments." What should come back: - An implementation plan tied to real runtime schemas. - Explicit handling of missing identifiers, refused calls and absent fields. - No invented package, tool arguments or source data. 8. 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 code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
The whole guide is also available as Markdown, for agents and LLMs: /connectors/zoho-crm/framework/claude-code.md
Zoho CRM tools Claude Code 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
Your app sends the request
It calls Agent200 with the model, instructions, the input, the end user's id and the Zoho CRM tools.
-
02
The model picks a tool
The model decides whether a Zoho CRM tool is needed, and with which arguments.
-
03
Agent200 runs the call
It uses that user's own Zoho CRM connection, within the endpoints and scopes your project allows, and returns the result to the model.
-
04
Your app gets the result
Agent200 returns the completed result. Your app decides when the agent runs and what happens next.
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.
