Scheduling & Booking · Integration
Zoho Calendar
Add Zoho Calendar to your product for your customers, and give your AI agents governed access to it.
Zoho Calendar addresses everything by uid. A calendar has one, an event has one, and neither is the display name a person would recognise, so the first thing an integration does is list the calendars a connected user actually has and hold on to their identifiers. The payload is the second surprise: event detail travels as a single eventdata parameter carrying the start, end and time zone together with attendees, reminders and an rrule holding the repeat pattern, so a series is described by a rule rather than by a list of dates and reading one occurrence is not the same as reading the series. There is also a flag deciding whether an event counts towards free and busy at all, which is how a personal note stays out of somebody's availability. Subscribed calendars are read only by nature. Calendar shares an account with the rest of a customer's Zoho suite but carries its own scopes, so the grant your product asks for is narrower than the account behind it.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each user connect their own Zoho Calendar so your product books time under their identity rather than a shared service account.
List a user's calendars first and map them by uid, because the name shown in the interface is not what the API addresses.
Create an event with its attendees, reminders and repeat rule in one call, and update the rule when the pattern changes.
Respect the free and busy flag, so an event your product adds for information alone does not make somebody look unavailable.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads what a user has booked for a day and proposes a time that does not clash with it.
An agent creates or reschedules an event within the scopes granted, with the calendar it wrote to recorded.
An agent points out that a repeat comes from a recurrence rule before anybody edits a single occurrence of it.
Example prompt
What is already booked on this calendar tomorrow, and where is there a clear hour for a review?
Set up Zoho Calendar in 4 steps
- 01Enable the Zoho Calendar connector in your fastn dashboard.
- 02Have each user grant the calendar scopes your features need and no more, remembering that the data centre their Zoho account was created in decides which API domain answers for them.
- 03List each user's calendars, store the uids you write to, and decide how your product handles repeat rules and free and busy.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Zoho Calendar integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Zoho Calendar integration without building it. Your customers connect their own Zoho Calendar account inside your product and work their bookings, events and availability there, with no per-customer code on your side.
- Handle the part that actually costs time: availability is only true at the moment you read it, so a stale free/busy picture becomes a double booking somebody has to apologise for. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Zoho Calendar update is not your on-call problem.
- One integration serves your product and your agents. The same governed Zoho Calendar connection powers in-product features and gives AI agents scoped, audited access, so you let people book and reschedule without leaving your product without wiring it twice.
Used by these teams
Compare with
Google CalendarWorks well with
Zoho MailOften used alongside
Tools the same teams tend to run next to Zoho Calendar, across other categories.
Slack
Microsoft Teams
Twilio
AircallZoho Calendar integration FAQ
How do I add a Zoho Calendar integration to my product?
Enable the Zoho Calendar connector in your fastn dashboard, then let each customer authenticate their own Zoho Calendar account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Zoho Calendar 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 Calendar account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Zoho Calendar account and only ever sees their own bookings, events and availability. 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 Calendar 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 reads what a user has booked for a day and proposes a time that does not clash with it.
Who maintains the Zoho Calendar integration?
fastn does. When Zoho Calendar 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.
Can my product create, reschedule or cancel bookings in Zoho Calendar automatically?
Yes, in each customer's own account. Your product reads live availability, places a booking, moves it or cancels it, and reacts when someone books or cancels on the other side.
Does it respect each team's own availability rules in Zoho Calendar?
Yes. Working hours, buffers, lead times, resource capacity and routing rules are configured per customer and mapped rather than hard-coded, so an unusual setup works without code from you.
What can I build with the Zoho Calendar integration?
A common starting point: let each user connect their own Zoho Calendar so your product books time under their identity rather than a shared service account. 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 Calendar integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Zoho Calendar does not change your per-connector cost. You can start free with 3 connected accounts.
Add Zoho Calendar to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.