Zoho Mail + Grok Bot
How to connect Zoho Mail to Grok Bot
Read email messages with Grok Bot and Agent200. Prepare a mailbox briefing using the connected user’s own Zoho Mail account.
On this page
Overview
Attach the Agent200 connector to the Grok Bot conversation and identify the email message to read. Name the source in your request so browser context or another connected app does not silently replace the requested tool read.
Start with one identified email message. Preserve the returned details, report missing information and keep the workflow read-only.
References: Grok Bot documentation and Zoho Mail provider reference.
- Connector
- Zoho Mail
- Works with
- Grok Bot · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 5 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 Mail enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Zoho Mail account. They approve access once, on Zoho Mail's own page.
- Grok Bot, with custom MCP servers allowed. Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.
Connect Zoho Mail to Grok Bot
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers Zoho Mail and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open the custom connector form
In Grok Bot, open Connect apps from the sidebar and choose Add a custom connector at the bottom.
-
3
Step 3: Fill in the server and your key
Enter the name Agent200, pick Type Remote HTTPS, enter the server URL and add one HTTP header:
Authorizationwith the valueBearerfollowed by your key. Leave Client ID empty, then choose Add plugin.Add a custom connectorMCP: Grok Bot custom connector form Name: Agent200 Type: Remote HTTPS Server URL: https://api.agent200.com/mcp/ HTTP headers: Authorization: Bearer YOUR_AGENT200_API_KEY -
4
Step 4: Attach Agent200 in a chat
In a Bot chat, type
@and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it. -
5
Step 5: Connect your Zoho Mail account
The first time you ask Grok Bot for something in Zoho Mail, Agent200 returns an authorization link. Open it and approve access on Zoho Mail's own page. Agent200 stores the connection and keeps it working; your password never reaches Grok Bot or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Use the Agent200 connector for this request. Read the Zoho Mail message I select from my connected mailbox. Summarize its sender, subject and the requested action stated in the body. Ask for missing account, folder or message context. Do not send, move, delete or change any message.
What should come back
- The selected email message is identified clearly.
- The answer includes only returned message identity, sender, subject and requested details from the body.
- Missing information and access failures are reported; no source data is changed.
Confirm the intended account, folder and message. Inspect the available tools and read permissions. Do not turn a missing body or access error into an invented email summary.
Get your API key
Create a key in the Agent200 dashboard. It reaches Zoho Mail 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 Mail to Grok Bot.
Goal: connect Zoho Mail to Grok Bot with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/zoho-mail/framework/grok-bot/ 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 Grok Bot's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Zoho Mail is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Grok Bot: 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 Grok Bot's exact menus or commands. 4. The first Zoho Mail request returns an authorization link if the user has not connected Zoho Mail yet: show it to them and continue once they have approved access on Zoho Mail's own page. 5. Check it works with this request: "Use the Agent200 connector for this request. Read the Zoho Mail message I select from my connected mailbox. Summarize its sender, subject and the requested action stated in the body. Ask for missing account, folder or message context. Do not send, move, delete or change any message." What should come back: - The selected email message is identified clearly. - The answer includes only returned message identity, sender, subject and requested details from the body. - 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 Mail, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/zoho-mail/framework/grok-bot.md
Zoho Mail tools Grok Bot can call
-
List mail accounts
Readzoho_mail_list_accountsIdentify the mail accounts available to the authenticated user.
-
List folders
Readzoho_mail_list_foldersFind folders within the mail account selected for the request.
-
List messages
Readzoho_mail_list_messagesRead a scoped list of messages from the selected account and folder.
-
Search messages
Readzoho_mail_search_messagesFind messages matching the requested search criteria in the selected account.
-
Read message content
Readzoho_mail_get_message_contentRetrieve the body of one selected message using its account, folder and message context.
No tool matches that search.
How it works
-
01
You ask Grok Bot
In your own words, for something in Zoho Mail.
-
02
Grok Bot picks a tool
It sees the Zoho Mail tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Zoho Mail connection, within the tools and scopes your project allows.
-
04
Grok Bot 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 Mail account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Zoho Mail enforces what its API grants.
Troubleshooting
The source cannot be read
Confirm the intended account, folder and message. Inspect the available tools and read permissions. Do not turn a missing body or access error into an invented email summary.
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
Does preparing a reply send an email?
No. Show proposed reply text in the conversation for review. This read-only guide does not configure sending, saving a provider-side draft or changing mailbox state.
How can I verify which connection Grok Bot used?
Inspect the tool activity and compare the returned record with the source you selected. A browser visit or another app’s response does not verify this Agent200 connection.
