Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Zoho Mail" |
| 4 | description: "Public support knowledge for Zoho Mail." |
| 5 | category: "toolkits-and-providers" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-06-24T00:00:00Z" |
| 8 | tags: |
| 9 | - "zoho_mail" |
| 10 | --- |
| 11 | # Zoho Mail |
| 12 | |
| 13 | |
| 14 | ## ZOHO_MAIL_MESSAGES_SEND_EMAIL supports sending attachments |
| 15 | |
| 16 | `ZOHO_MAIL_MESSAGES_SEND_EMAIL` supports sending attachments. If a customer previously saw missing attachment support, ask them to retry on the latest/current toolkit behavior and share the tool call details if attachment sending still fails. |
| 17 | |
| 18 | ## Pass the correct Zoho region when connecting Zoho Mail |
| 19 | |
| 20 | For Zoho Mail connection issues, verify the region passed during connection initiation. Zoho accounts can be region-specific, so an EU or other regional account may fail if the default/wrong region is used. Retry the connection with the correct Zoho region. |
| 21 | |
| 22 | ## Zoho Mail account_id must be handled as a string to avoid JavaScript precision loss |
| 23 | |
| 24 | Treat Zoho Mail `account_id` values as strings, not integers. Zoho account IDs can exceed JavaScript's safe integer limit, and numeric coercion can silently truncate them before the tool call reaches Zoho. If a customer sees unexpected account IDs or tool failures with long IDs, verify the schema and payload preserve `account_id` as a string. |
| 25 | |
| 26 | ## Connect MCP is agent-oriented; authenticate Zoho Mail in Connect dashboard before tool use |
| 27 | |
| 28 | Connect MCP is intended for agent/client workflows through Tool Router, not as a raw direct API endpoint. For Zoho Mail, make sure the user has connected a Zoho Mail account in the Connect dashboard first, then use the supported MCP client flow. If the user wants direct API execution, route them to Tool Router/API or Proxy Execute patterns instead of treating Connect MCP as a raw REST proxy. |