Zoho CRM + OpenClaw
How to connect Zoho CRM to OpenClaw
Read CRM records with OpenClaw and Agent200. Prepare a sales briefing using the connected user’s own Zoho CRM account.
On this page
Overview
Saving an Agent200 server configuration is the first check. Confirm tool discovery, then read one CRM record the connected user can access. The returned source record verifies the Zoho CRM path; a saved setting alone does not.
Start with one identified CRM record. Preserve the returned details, report missing information and keep the workflow read-only.
References: OpenClaw documentation and Zoho CRM provider reference.
- Connector
- Zoho CRM
- Works with
- OpenClaw · 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.
- OpenClaw, with custom MCP servers allowed. OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.
Connect Zoho CRM to OpenClaw
-
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: Store your key in ~/.openclaw/.env
OpenClaw fills
${AGENT200_API_KEY}in its config from~/.openclaw/.env, so the key never sits in the config itself.~/.openclaw/.envMCP: OpenClaw key in ~/.openclaw/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Save the server
openclaw mcp settakes one JSON object. Always set the transport tostreamable-http: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves${AGENT200_API_KEY}for OpenClaw. In the Control UI, add it under Settings > MCP, then put the header in the config editor on the same page.Stop the Gateway before CLI changes or live probes against its state. Use the Control UI for supported changes while it is running.
TerminalMCP: OpenClaw save the server from the CLI openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}' -
4
Step 4: Probe the server
Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.
TerminalMCP: OpenClaw probe the server openclaw mcp doctor agent200 --probe openclaw mcp status --verbose -
5
Step 5: Authorize the intended Zoho CRM account
Complete the authorization flow for the intended user. Confirm access to the selected CRM record before running the test.
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 OpenClaw.
Goal: connect Zoho CRM to OpenClaw with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/zoho-crm/framework/openclaw/ 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 OpenClaw'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 OpenClaw: 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 OpenClaw'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/openclaw.md
Zoho CRM tools OpenClaw 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 OpenClaw
In your own words, for something in Zoho CRM.
-
02
OpenClaw 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
OpenClaw 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.
Does saving the MCP configuration prove the read works?
No. Verify tool discovery and then perform the selected source read. Check both the active server configuration and the connected user if discovery succeeds but access fails.
