Zoho Bookings
List workspaces, services and staff, check availability, and book, get, update, reschedule and cancel appointments in Zoho Bookings, across every Zoho data centre.
About
Zoho Bookings ships in the w6w first-party pack. It declares 9 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.zoho-bookings- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Calendar & Scheduling
Overview
Zoho Bookings runs a business’s appointment scheduling — workspaces (locations), services, staff and the appointments customers book against them. This app covers Zoho’s documented v1 API end to end: list workspaces/services/staff, fetch open slots for a service, book an appointment, look one up, update its status (complete, cancel or mark no-show), reschedule it to a different time or staff, and add a new staff member.
Zoho hosts every account in one of eight regional data centres, each with its own API host, so this app routes each region through its own dedicated connection rather than one that could silently send a EU account’s requests through the US region instead. Canada is the one region where the OAuth host breaks the naming pattern the other seven follow, and this app points at the real host rather than the one the pattern would suggest.
Zoho Bookings’ v1 API is a small, single-scope surface — one OAuth scope covers every documented call, and there is no separate customer list, recurring-appointment, payment, or resource-management endpoint published, so none of those are attempted here.
Build with Zoho Bookings
Three routes to the same 9 actions. The Workflow tab is generated from Zoho Bookings'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.
Reschedule Appointment
appointment-reschedule Move a booked appointment to a different time and/or a different staff member or group. At least one of Staff ID, Group ID or Start time is required.
Update Appointment Status
appointment-update Mark a booked appointment completed, cancelled or a no-show.
List Available Slots
availability-list Fetch open appointment slots for a service on a given date. Exactly one of Staff ID / Group ID / Resource ID is required alongside Service ID and Selected Date.
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 Bookings's real ids.
{
"manifestVersion": "2",
"name": "zoho-bookings-example",
"steps": [
{
"id": "appointment-book",
"uses": {
"app": "io.w6w.zoho-bookings",
"action": "appointment-book",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"serviceId": "<serviceId>",
"fromTime": "<fromTime>",
"customerName": "<customerName>"
}
}
]
}Here are some of the things you can do
-
Book Appointment
performappointment-book -
Get Appointment
readappointment-get -
Reschedule Appointment
performappointment-reschedule -
Update Appointment Status
performappointment-update -
List Available Slots
readavailability-list
+4 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 Bookings, 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 Bookings. 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: "appointment-book",
payload: {
serviceId: "<value>",
// staffId: "<value>",
// resourceId: "<value>",
// groupId: "<value>",
fromTime: "<value>",
// toTime: "<value>",
// timezone: "<value>",
customerName: "<value>",
customerEmail: "<value>",
// customerPhone: "<value>",
// notes: "<value>",
// additionalFields: "<value>",
// costPaid: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action appointment-book --payload '{"serviceId":"<value>","fromTime":"<value>","customerName":"<value>","customerEmail":"<value>"}'Give an AI agent Zoho Bookings — without giving it Zoho Bookings'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-bookings#appointment-book",
"input": {
"serviceId": "<serviceId>",
"fromTime": "<fromTime>",
"customerName": "<customerName>"
}
}
}
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 Bookings 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 Bookings'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 Bookings itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Zoho Bookings declares its own checks, so its health is a property of the app rather than something the host guesses at.
Zoho Bookings platform status
Reads the "Zoho Bookings" component off Zoho's StatusIQ RSS feed (us.zohostatus.com/rss). Unauthenticated and unsigned.