Zoho Calendar
Create, read, update and delete calendars and events in Zoho Calendar, across every Zoho data centre.
About
Zoho Calendar ships in the w6w first-party pack. It declares 13 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.zoho-calendar- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Calendar & Scheduling · Productivity
Overview
Zoho Calendar puts a user’s schedule into a workflow — list, read, create, update and delete calendars; list, read, create, update and delete events (including recurring ones via RRULE or the structured repeat object); search event titles within a calendar; read a group’s RSVP status for an event; and check a user’s free/busy availability across all their calendars.
Zoho hosts every account in one of eight regional data centres, each with its own API host and its own OAuth (accounts) host, so this app routes each region through its own dedicated connection rather than one that could silently send an EU user’s requests through the US region instead. Canada is the one region where BOTH of those hosts break the naming pattern the other seven follow, and this app points at the real hosts rather than the ones the pattern would suggest.
Updating an event replaces the entire event resource rather than patching it — this app requires the event’s current etag (from Get Event) on every update/delete and documents the replace-not-patch behavior loudly, since Zoho itself does. File attachments, moving an event between calendars, and adding a live Zoho Meeting conference link are deliberately left out: the first needs multipart upload, the second a non-standard HTTP verb, and the third a separate OAuth scope this app does not request, all outside this app’s JSON-only, single-scope action set.
Build with Zoho Calendar
Three routes to the same 13 actions. The Workflow tab is generated from Zoho Calendar's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Delete Event
event-delete Delete an event (or one instance of a recurring event). `etag` is required — get the current value from Get Event.
Get Event
event-get Get one event's details, including its current `etag` (needed to update/delete).
Get Group Attendees
event-group-attendees-get Get the RSVP status of one invited group's members for an event.
Update Event
event-update Replace an existing event. This OVERWRITES every field with what you send here — fields you omit are cleared, not left alone. Fetch the event first (Get Event) if you only mean to change one thing. `start`, `end` and `etag` are required.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Zoho Calendar's real ids.
{
"manifestVersion": "2",
"name": "zoho-calendar-example",
"steps": [
{
"id": "calendar-create",
"uses": {
"app": "io.w6w.zoho-calendar",
"action": "calendar-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"name": "<name>",
"color": "<color>"
}
}
]
}Here are some of the things you can do
-
Create Calendar
performcalendar-create -
Get Calendar
readcalendar-get -
List Calendars
readcalendar-list -
Update Calendar
performcalendar-update -
Create Event
performevent-create
+8 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Zoho Calendar, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Zoho Calendar. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "calendar-create",
payload: {
name: "<value>",
color: "<value>",
// description: "<value>",
// textcolor: "<value>",
// timezone: "<value>",
// includeInFreebusy: "<value>",
// private: "<value>",
// public: "<value>",
// reminders: "<value>",
// status: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action calendar-create --payload '{"name":"<value>","color":"<value>"}'Give an AI agent Zoho Calendar — without giving it Zoho Calendar's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.zoho-calendar#calendar-create",
"input": {
"name": "<name>",
"color": "<color>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Zoho Calendar connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Zoho Calendar's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Zoho Calendar itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Zoho Calendar declares its own checks, so its health is a property of the app rather than something the host guesses at.
Zoho Calendar platform status
Reads the "Zoho Calendar" component off Zoho's StatusIQ RSS feed (us.zohostatus.com/rss). Unauthenticated and unsigned.