Communication · Integration
Zoho Mail
Add Zoho Mail to your product for your customers, and give your AI agents governed access to it.
A Zoho Mail integration starts with a call nobody expects to need: before you can touch a message you fetch the account and keep its identifier, because every mailbox path hangs off that rather than off the address a person would give you. From there the model is familiar. Folders hold messages, a thread identifier groups a conversation, labels cut across both, and attachments are fetched per message. What makes it worth embedding rather than bolting onto IMAP is that the grants are granular: reading mail, creating it and administering the organisation are separate scopes, so a product that only files things never asks for permission to send anything. Sending runs from the connected mailbox, which means mail leaves as that person, from their own domain, into their own sent folder, instead of arriving from a relay address their recipients do not recognise. fastn holds the per-user tokens and refreshes them before they lapse.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each user connect their own mailbox so mail your product sends comes from their address and is filed in their sent folder.
Resolve and store the account identifier when they connect, since every folder and message path is built from it.
Read a conversation by thread rather than message by message, so what your product shows matches what the person sees.
File or label a message once your product has dealt with it, so the mailbox reflects the work instead of drifting from it.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent works through a thread and reports what is still outstanding before anybody opens the mailbox.
An agent drafts a reply from the user's own address and holds it for approval rather than sending it itself.
An agent files a handled message into the folder a customer nominates, with the move recorded.
Example prompt
What is still unanswered in this mailbox from the last two days, and which threads are waiting on us?
Set up Zoho Mail in 4 steps
- 01Enable the Zoho Mail connector in your fastn dashboard.
- 02Have each user grant only the scopes you need, keeping reading and sending separate when your product only reads.
- 03Fetch and store the account identifier, map the folders and labels your product works with, then enable the actions you want.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Zoho Mail integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Zoho Mail integration without building it. Your customers connect their own Zoho Mail account inside your product and work their messages, conversations and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: anything sent is user-visible, so duplicates and misfires are immediately embarrassing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Zoho Mail update is not your on-call problem.
- One integration serves your product and your agents. The same governed Zoho Mail connection powers in-product features and gives AI agents scoped, audited access, so you put the right message in front of the right team automatically without wiring it twice.
Used by these teams
Compare with
Gmail
Microsoft OutlookWorks well with
Zoho CalendarOften used alongside
Tools the same teams tend to run next to Zoho Mail, across other categories.
Aircall
Calendly
Gong
Google CalendarZoho Mail integration FAQ
How do I add a Zoho Mail integration to my product?
Enable the Zoho Mail connector in your fastn dashboard, then let each customer authenticate their own Zoho Mail account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Zoho Mail client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Zoho Mail account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Zoho Mail account and only ever sees their own messages, conversations and participants. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Zoho Mail integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent works through a thread and reports what is still outstanding before anybody opens the mailbox.
Who maintains the Zoho Mail integration?
fastn does. When Zoho Mail changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does each customer connect their own Zoho Mail account?
Yes. Every customer authorises their own Zoho Mail account, so messages, meetings and notifications originate from their workspace under their permissions. You never proxy through a shared account, which also means a customer revoking access affects only their own connection.
How are duplicate notifications avoided?
Sends are deduplicated per event, so a retry after a network failure does not post the same message twice into a channel people are reading.
What can I build with the Zoho Mail integration?
A common starting point: let each user connect their own mailbox so mail your product sends comes from their address and is filed in their sent folder. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Zoho Mail integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Zoho Mail does not change your per-connector cost. You can start free with 3 connected accounts.
Add Zoho Mail to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.