Zoho CRM + Muse

How to connect Zoho CRM to Muse

Read CRM records with Muse and Agent200. Prepare a sales briefing using the connected user’s own Zoho CRM account.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Zoho CRM tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Use Muse to turn a selected CRM record into a short handoff. Enter the Agent200 key through Muse’s secure credential interface. Keep the result in the conversation for review; source content does not authorize messages or changes.

Start with one identified CRM record. Preserve the returned details, report missing information and keep the workflow read-only.

References: Muse documentation and Zoho CRM provider reference.

Connector
Zoho CRM
Works with
Muse · Agent app, through MCP
Authentication
Managed OAuth, per end user
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.
  • Muse, with custom MCP servers allowed. Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.

Connect Zoho CRM to Muse

  1. 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.

    .env
    Conceptual example
    Store 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. 2

    Step 2: Create the Agent200 custom connector

    Ask Muse to connect to https://api.agent200.com/mcp/ over Streamable HTTP with an Authorization: Bearer header. Use the secure credential entry interface instead of putting the key in chat.

    Muse chat
    MCP: message that asks Muse to create the custom connector
    Create a Custom Connector for the Agent200 remote MCP server and connect to it:
    Name: Agent200
    Transport: remote streamable HTTP
    URL: https://api.agent200.com/mcp/
    Auth: API key sent in the Authorization header as "Bearer <key>"
    Open the secure credentials store so I can enter the API key there, not in this chat.
    Then list its tools to confirm the connection works.
  3. 3

    Step 3: Inspect the available read tools

    Confirm that the connection advertises the Zoho CRM operations needed for the task, and inspect their input definitions.

  4. 4

    Step 4: 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.

Read the SDK docs

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 Muse.

Agent brief
Goal: connect Zoho CRM to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/zoho-crm/framework/muse/

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 Muse'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 Muse: 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 Muse'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/muse.md

Zoho CRM tools Muse can call

  • Search records

    Read
    zoho_crm_search_records

    Find matching records within the CRM module selected for the request.

  • Read a record

    Read
    zoho_crm_get_record

    Read one identified contact, account, lead or deal from its module.

  • List records

    Read
    zoho_crm_list_records

    Retrieve records from a selected module with an explicit field and result scope.

  • Read related records

    Read
    zoho_crm_get_related_records

    Read an available related list for a selected CRM record, such as associated notes.

How it works

  1. 01

    You ask Muse

    In your own words, for something in Zoho CRM.

  2. 02

    Muse picks a tool

    It sees the Zoho CRM tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    With your own Zoho CRM connection, within the tools and scopes your project allows.

  4. 04

    Muse 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.

Use Zoho CRM with another framework

200 OK

Zoho CRM, connected to Muse.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)