> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/zoho-desk.md).

# Zoho Desk

Zoho Desk help desk and knowledge base. Connect to index articles.

* Knowledge base source
* MCP connection

## Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector       | Authentication |
| --------------- | -------------- |
| Zoho Desk       | OAuth sign-in  |
| Zoho Desk (API) | Credentials    |
| Zoho Desk (MCP) | MCP with OAuth |

### Zoho Desk

Connect to Zoho Desk to index knowledge base articles.

#### Set up in Zoho Desk

1. Use a Zoho Desk account with access to the records and operations that your workflow needs.
2. If your organization restricts application access or user consent, have its administrator approve the connection before you sign in.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **Zoho Desk**.
2. Select **Connect**, sign in to the provider account, and review the requested access. Complete authorization to return to StackAI.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

StackAI obtains the OAuth credentials during sign-in. You do not need to paste an access token or refresh token.

### Zoho Desk (API)

Connect to Zoho Desk with Organization ID and OAuth access token (Zoho-oauthtoken). Use for knowledge base article indexing.

#### Set up in Zoho Desk

1. Sign in to Zoho Desk and find your organization ID (orgId) under Setup → Developer Space → API.
2. Create a Self Client in the Zoho API Console (<https://api-console.zoho.com/>) to obtain OAuth credentials, then generate an access token with the Desk scopes you need.
3. Copy the access token; it is sent as a 'Zoho-oauthtoken' authorization value on API requests.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **Zoho Desk (API)**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field   | Required                 | What to enter                                                                                  |
| --------------- | ------------------------ | ---------------------------------------------------------------------------------------------- |
| Access Token    | Yes                      | Zoho OAuth access token. With Refresh Token + Client ID/Secret, it is refreshed automatically. |
| Refresh Token   | Optional / as applicable | Optional. With Client ID and Secret, access token is refreshed automatically (recommended).    |
| Client Secret   | Optional / as applicable | Required for token refresh.                                                                    |
| Scopes          | Optional / as applicable | Permission scopes for this connection.                                                         |
| Organization ID | Yes                      | Your Zoho Desk organization ID. Required for all API requests.                                 |
| API Domain      | Optional / as applicable | Zoho data center: com, eu, in, au. Default: com.                                               |
| Client ID       | Optional / as applicable | Required for token refresh. From your Zoho API Console client.                                 |

**Provider documentation:** [Setup reference](https://desk.zoho.com/DeskAPIDocument).

### Zoho Desk (MCP)

Connect to Zoho's Remote MCP server for AI-powered access to your Zoho Desk tickets and knowledge base. Uses Zoho's native MCP OAuth authentication.

#### Set up in Zoho Desk

1. Sign in to the Zoho MCP portal and create a server for your organization.
2. Add Zoho Desk to that server and enable the tools you want StackAI to use.
3. Copy the server URL from the MCP portal. The regular Zoho Desk account URL is not an MCP server URL.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **Zoho Desk (MCP)**.
2. Complete the connector configuration below. If you do not have access to these settings, ask your StackAI administrator to configure the connector.
3. Select **Connect**, sign in to the provider account, and review the requested access. Complete authorization to return to StackAI.
4. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connector configuration**

| StackAI field | Required  | What to enter                                                                                                                                                                                                                                                                                                                                                                                                                   |
| ------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Server URL    | Yes       | Your per-tenant Zoho MCP server URL. This comes from the Zoho MCP portal, not the regular Zoho Desk admin. Setup steps: (1) Sign in to the Zoho MCP portal and create a new MCP server for your org. (2) Add the Zoho Desk app to that server. (3) Enable the specific tools you want exposed — without this, the connection will be healthy but show 0 tools. (4) Copy the 'Server URL' shown in the portal and paste it here. |
| Scopes        | Read-only | OAuth scope required by Zoho's MCP server. This value is shown for reference; it is not an editable credential.                                                                                                                                                                                                                                                                                                                 |

**Connection notes**

* A healthy connection can still list no tools if the tools have not been enabled in the Zoho MCP portal.

### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

## Important behavior

If an operation is denied, check the connection’s granted permissions and the account’s access in the provider. Reauthorize the connection when it needs additional permissions.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/zoho-desk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
