Zoho Sheet
Read and write Zoho Sheet workbooks, worksheets, rows and ranges.
About
Zoho Sheet ships in the w6w first-party pack. It declares 10 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.zoho-sheet- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Spreadsheets · Productivity
Overview
Zoho Sheet puts an online spreadsheet into a workflow — list and create workbooks, list, create and delete the worksheets inside them, and read or write the rows and ranges those worksheets hold. Appending JSON rows after a worksheet’s last used row is the common sync case; writing a CSV block at a given cell and clearing a range’s content cover the rest of routine read/write automation, and a used-area lookup lets a workflow size a range or find the next free row without reading a worksheet’s content first.
Zoho hosts every account in one of seven regional data centres (there is no Canadian Zoho Sheet API host), each with its own connection endpoint, so this app routes each region through its own dedicated connection rather than one that could silently send a request to the wrong region’s host.
Tabular “Data Store” table operations, pivot tables, charts, conditional formatting, mail-merge, named ranges/data-validation, and workbook sharing/versioning/publish/upload/download are deliberately left out as either a different mental model from plain spreadsheet CRUD or large enough to warrant their own action set later.
Build with Zoho Sheet
Three routes to the same 10 actions. The Workflow tab is generated from Zoho Sheet'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.
Write Range (CSV)
sheet-write-csv Overwrite a range with CSV data, starting at a given cell. Existing content in the overwritten cells is replaced.
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 Sheet's real ids.
{
"manifestVersion": "2",
"name": "zoho-sheet-example",
"steps": [
{
"id": "sheet-append",
"uses": {
"app": "io.w6w.zoho-sheet",
"action": "sheet-append",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"resourceId": "<resourceId>",
"jsonData": "<jsonData>"
}
}
]
}Here are some of the things you can do
-
Append Rows
performsheet-append -
Clear Range
performsheet-clear -
Create Sheet
performsheet-create -
List Sheets
readsheet-list -
Read Rows
readsheet-read
+5 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 Sheet, 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 Sheet. 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: "sheet-append",
payload: {
resourceId: "<value>",
// worksheetName: "<value>",
// worksheetId: "<value>",
// headerRow: "<value>",
jsonData: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action sheet-append --payload '{"resourceId":"<value>","jsonData":"<value>"}'Give an AI agent Zoho Sheet — without giving it Zoho Sheet'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-sheet#sheet-append",
"input": {
"resourceId": "<resourceId>",
"jsonData": "<jsonData>"
}
}
}
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 Sheet 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 Sheet'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 Sheet itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Zoho Sheet declares its own checks, so its health is a property of the app rather than something the host guesses at.
Zoho Sheet platform status
Reads the "Zoho Sheet" component off Zoho's StatusIQ RSS feed (us.zohostatus.com/rss). Unauthenticated and unsigned.