# Connect Zoho Desk to Muse Prepare a grounded support queue briefing

> Read tickets with Muse and Agent200. Prepare a support queue briefing using the connected user’s own Zoho Desk account.

- Page: https://www.agent200.com/connectors/zoho-desk/framework/muse/
- Connector: [Zoho Desk](https://www.agent200.com/connectors/zoho-desk.md)
- Framework: Muse
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect Zoho Desk to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/zoho-desk/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 Desk 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 Desk request returns an authorization link if the user has not connected Zoho Desk yet: show it to them and continue once they have approved access on Zoho Desk's own page.
5. Check it works with this request: "Read the Zoho Desk ticket I identify and prepare a support queue briefing. Name the source and use only ticket status, subject, contact and owner fields. State access gaps; do not change records."
   What should come back:
   - The selected ticket is identified.
   - Only the returned ticket status, subject, contact and owner fields are reported.
   - Access gaps and missing context are explicit; 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 Desk, then retry.

## Overview

Use Muse to prepare a short support queue briefing for review. Put the Agent200 key in Muse’s secure credential interface, then inspect the source before sharing the result.

Start with one identified ticket. Preserve returned ticket status, subject, contact and owner fields; report missing data and keep the workflow read-only.

Provider reference: [Zoho Desk API](https://desk.zoho.com/DeskAPIDocument).

- **Connector:** [Zoho Desk](https://www.agent200.com/connectors/zoho-desk/)
- **Works with:** Muse · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [5 tools](https://www.agent200.com/connectors/zoho-desk/framework/muse/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Zoho Desk enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a Zoho Desk account.** They approve access once, on Zoho Desk'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 Desk to Muse

### Step 1: Create your Agent200 API key

Create a key on the [API keys page](https://agent200.com/platform/apikeys/) and store it securely.

File `.env`:

```bash
# Keep the key out of your code, prompts and chats.
export AGENT200_API_KEY="paste-your-key-here"
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Create the custom connector

Connect to `https://api.agent200.com/mcp/` over Streamable HTTP with an Authorization: Bearer header. Enter the key in Muse’s secure credential interface.

File `Muse chat`:

```text
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.
```

### Step 3: Inspect read tools

Confirm the Zoho Desk operations and schemas advertised by the connection.

### Step 4: Authorize Zoho Desk

Connect the intended user and test one accessible ticket.

## Test your connection

Ask: "Read the Zoho Desk ticket I identify and prepare a support queue briefing. Name the source and use only ticket status, subject, contact and owner fields. State access gaps; do not change records."

What should come back:

- The selected ticket is identified.
- Only the returned ticket status, subject, contact and owner fields are reported.
- Access gaps and missing context are explicit; no source data is changed.

Check the selected ticket ID, account scope, read permission and pagination. Tickets can contain customer data. Scope by department and pagination; do not imply a reply or status change from a drafted answer.

## Zoho Desk tools Muse can call

- **List tickets** (`zoho_desk_list_tickets`, read): Find tickets in the accessible department.
- **Read a ticket** (`zoho_desk_get_ticket`, read): Retrieve one identified ticket.
- **List contacts** (`zoho_desk_list_contacts`, read): Find support contacts in scope.
- **Read a contact** (`zoho_desk_get_contact`, read): Retrieve one identified support contact.
- **List departments** (`zoho_desk_list_departments`, read): Find departments available to the connection.

## How it works

1. **You ask Muse.** In your own words, for something in Zoho Desk.
2. **Muse picks a tool.** It sees the Zoho Desk tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own Zoho Desk connection, within the tools and scopes your project allows.
4. **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 Desk account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and Zoho Desk enforces what its API grants.

## Troubleshooting

### The source cannot be read

Check the selected ticket ID, account scope, read permission and pagination. Tickets can contain customer data. Scope by department and pagination; do not imply a reply or status change from a drafted answer.

## FAQ

### How do I verify this result?

Compare the named ticket and returned ticket status, subject, contact and owner fields with the source. Treat missing information as missing, not as a fact.

## Use Zoho Desk with another framework

- [Zoho Desk + Claude](https://www.agent200.com/connectors/zoho-desk/framework/claude.md)
- [Zoho Desk + ChatGPT](https://www.agent200.com/connectors/zoho-desk/framework/chatgpt.md)
- [Zoho Desk + Claude Code](https://www.agent200.com/connectors/zoho-desk/framework/claude-code.md)
- [Zoho Desk + Grok Bot](https://www.agent200.com/connectors/zoho-desk/framework/grok-bot.md)
- [Zoho Desk + OpenAI Dots](https://www.agent200.com/connectors/zoho-desk/framework/openai-dots.md)
- [Zoho Desk + Claude Duet](https://www.agent200.com/connectors/zoho-desk/framework/claude-duet.md)
- [Zoho Desk + Hermes Agent](https://www.agent200.com/connectors/zoho-desk/framework/hermes-agent.md)
- [Zoho Desk + OpenClaw](https://www.agent200.com/connectors/zoho-desk/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
