Zoho Sign
Upload documents, send them for signature, and manage templates in Zoho Sign, across every Zoho data centre.
About
Zoho Sign ships in the w6w first-party pack. It declares 12 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.zoho-sign- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Documents & Files · Legal & Compliance · Productivity
Overview
Zoho Sign is how a document gets signed — upload it, record who needs to sign and in what order, send it out, track its status, and clean up afterward — and this app covers that lifecycle over Zoho Sign’s own REST API.
It creates a document draft from an uploaded file and a list of recipients, sends it out for signature, lists and reads request status, recalls or deletes a request, and sends a reminder to whoever hasn’t signed yet. On the template side it uploads a reusable template with recipient roles, reads back the fields a document created from it needs, fills those roles with real people and sends the result for signature in one call, and deletes a template.
Zoho hosts every organization in one of ten regional data centres, each with its own dedicated sign.zoho.<tld> API host and (almost always) its own accounts.zoho.<tld> OAuth host, so this app routes each region through its own dedicated connection rather than one that could silently send a UK organization’s requests through the US region instead. Canada is the one region where BOTH of those hosts break the naming pattern the other nine follow, and this app points at the real endpoints rather than the ones the pattern would suggest.
User management, folder management, document-type/field-type administration, PDF and completion-certificate download, full field-by-field re-placement on update, signer groups, and Aadhaar/e-stamping are deliberately left out — either their exact endpoints were never located in Zoho’s documentation, or they are a large editor-shaped surface this app does not attempt to model generically. See README.md for the complete list.
Build with Zoho Sign
Three routes to the same 12 actions. The Workflow tab is generated from Zoho Sign'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.
Create Document (Draft)
request-create Upload a document and record its recipients as a draft signature request. Nobody is notified until Send Document For Signature runs.
Recall Request
request-recall Cancel an in-progress signature request. Recipients can no longer sign it.
Send Document For Signature
request-submit Submit a draft request (from Create Document) for signature.
Create Template
template-create Upload a document and define its recipient roles as a reusable template.
Send Document Using Template
template-create-document Fill a template's recipient roles with real people and send it for signature.
Get Template
template-get Get a template's details, including the fields a document created from it needs.
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 Sign's real ids.
{
"manifestVersion": "2",
"name": "zoho-sign-example",
"steps": [
{
"id": "request-create",
"uses": {
"app": "io.w6w.zoho-sign",
"action": "request-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"requestName": "<requestName>",
"file": "<file>",
"actions": "<actions>"
}
}
]
}Here are some of the things you can do
-
Create Document (Draft)
performrequest-create -
Get Request
readrequest-get -
List Requests
readrequest-list -
Recall Request
performrequest-recall -
Remind Recipient
performrequest-remind
+7 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 Sign, 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 Sign. 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: "request-create",
payload: {
requestName: "<value>",
file: "<value>",
actions: "<value>",
// notes: "<value>",
// isSequential: "<value>",
// expirationDays: "<value>",
// emailReminders: "<value>",
// reminderPeriod: "<value>",
// folderId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action request-create --payload '{"requestName":"<value>","file":"<value>","actions":"<value>"}'Give an AI agent Zoho Sign — without giving it Zoho Sign'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-sign#request-create",
"input": {
"requestName": "<requestName>",
"file": "<file>",
"actions": "<actions>"
}
}
}
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 Sign 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 Sign'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 Sign itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Zoho Sign declares its own checks, so its health is a property of the app rather than something the host guesses at.
Zoho Sign platform status
Reads the "Zoho Sign" component off Zoho's StatusIQ RSS feed (us.zohostatus.com/rss). Unauthenticated and unsigned.