# How to connect Zoho Sign to Claude

```json
{
  "title": "How to connect Zoho Sign to Claude",
  "toolkit": "Zoho Sign",
  "toolkit_slug": "zoho_sign",
  "framework": "Claude Cowork",
  "framework_slug": "claude-cowork",
  "url": "https://composio.dev/toolkits/zoho_sign/framework/claude-cowork",
  "markdown_url": "https://composio.dev/toolkits/zoho_sign/framework/claude-cowork.md",
  "updated_at": "2026-11-06T07:08:25.203Z"
}
```

## Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.
This guide walks you through the easiest and most secure way to connect your Zoho Sign account to Claude via Composio Connect, enabling it to list pending Zoho Sign requests needing signatures, send a contract for Zoho Sign signatures, check signing status for recent Zoho documents, and more such actions on your behalf without compromising your account security.
Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.
For exact tool slugs and parameter tables, see the [tool catalog in the Composio docs](https://docs.composio.dev/toolkits/zoho_sign).

## Also integrate Zoho Sign with

- [ChatGPT](https://composio.dev/toolkits/zoho_sign/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/zoho_sign/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/zoho_sign/framework/atomic-agent)

## Connect Zoho Sign to Claude Cowork

### Connecting Zoho Sign to Claude Web, Desktop, and Cowork
Two ways to add the Composio connector. Pick whichever you prefer.
### 1. Add with one click
Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.
[Add to Claude](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Composio&connectorUrl=https%3A%2F%2Fconnect.composio.dev%2Fmcp)
### Add manually
In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.
Click Add custom connector and paste in the Composio MCP server URL:

```bash
https://connect.composio.dev/mcp
```

## What is the Zoho Sign MCP server, and what's possible with it?

The Zoho Sign MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Zoho Sign account. It provides structured and secure access to electronic signature workflows, documents, templates, recipients, and organization resources, so your agent can create, send, track, and manage signature requests on your behalf.
- Create and send signature requests: Have your agent upload PDF documents or use Zoho Sign templates to prepare requests, add recipients and signer fields, then submit them for signing.
- Track signing progress: Let the agent check request status, review recipients and signer fields, list pending requests, and send reminders to recipients who have not signed.
- Manage templates and reusable workflows: Direct your agent to create, list, inspect, merge, update, or delete templates, and create requests from one or more compatible templates.
- Handle completed documents: Instruct your agent to download signed documents, retrieve completion certificates, email completed requests, or read field values entered during signing.
- Organize Zoho Sign resources: Have your agent manage folders, signer groups, request types, users, organization details, and draft requests, including requests that need correction or recall.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `ZOHO_SIGN_CREATE_FOLDER` | Create Folder | Create a persistent Zoho Sign folder. Zoho Sign provides no folder-delete API endpoint, so this action cannot automatically clean up the folder. |
| `ZOHO_SIGN_CREATE_REQUEST` | Create Request | Upload 1-40 PDF documents and create a Zoho Sign draft request. This action does not send the request to recipients. |
| `ZOHO_SIGN_CREATE_REQUEST_FROM_MERGED_TEMPLATES` | Create Request From Merged Templates | Create one Zoho Sign request from two or more compatible templates. quick_send=true immediately submits the request and irreversibly emails external recipients, requiring a paid API-capable plan and submission credits. This endpoint's page does not guarantee that quick_send=false creates a draft, so use false only when that uncertainty is acceptable. |
| `ZOHO_SIGN_CREATE_REQUEST_FROM_TEMPLATE` | Create Request From Template | Create a Zoho Sign request from a template. quick_send must be chosen explicitly: true irreversibly emails external recipients and requires a paid API-capable plan and send credits; false creates an editable draft. |
| `ZOHO_SIGN_CREATE_REQUEST_TYPE` | Create Request Type | Create a persistent Zoho Sign document/request type. Zoho Sign provides no request-type delete API endpoint, so this action cannot automatically clean up the request type. |
| `ZOHO_SIGN_CREATE_SIGNER_GROUP` | Create Signer Group | Create a persistent Zoho Sign signer group with named email recipients. Zoho Sign provides no signer-group delete API endpoint, so this action cannot automatically clean up the group. |
| `ZOHO_SIGN_CREATE_TEMPLATE` | Create Template | Upload 1-40 PDF documents and create a reusable Zoho Sign template with recipient roles and signer fields. |
| `ZOHO_SIGN_DELETE_DOCUMENT` | Delete Document | Permanently delete one document file from an owned Zoho Sign request. This destructive action cannot be undone and does not delete the whole request. |
| `ZOHO_SIGN_DELETE_REQUEST` | Delete Request | Destructively move an owned Zoho Sign request to trash. This is a soft delete rather than immediate permanent erasure. Optionally recall an in-progress request first, which stops its remaining signing process. |
| `ZOHO_SIGN_DELETE_TEMPLATE` | Delete Template | Destructively move an owned reusable Zoho Sign template to trash. This is a soft delete rather than immediate permanent erasure. |
| `ZOHO_SIGN_DOWNLOAD_COMPLETION_CERTIFICATE` | Download Completion Certificate | Download the PDF completion certificate for a fully signed request. Draft and in-progress requests do not have a certificate; completing a request through the API requires a paid API-capable Zoho Sign plan and credits. |
| `ZOHO_SIGN_DOWNLOAD_DOCUMENT` | Download Document | Download one PDF document from a Zoho Sign request. |
| `ZOHO_SIGN_DOWNLOAD_REQUEST` | Download Request | Download all documents in a Zoho Sign request as a PDF or ZIP, optionally merged and including the completion certificate. |
| `ZOHO_SIGN_EMAIL_COMPLETED_REQUEST` | Email Completed Request | Immediately email an owned completed Zoho Sign request to one to three addresses. The request must have completed signing, which generally depends on the paid API submission workflow. This sends real external email; confirm every destination before calling, and check delivery before retrying to avoid duplicate messages. |
| `ZOHO_SIGN_EXTEND_REQUEST` | Extend Request | Extend the signing-link expiration date of an owned sent request. The request must already have been submitted through Zoho Sign's paid, credit-consuming API-send workflow. |
| `ZOHO_SIGN_GENERATE_EMBEDDED_SIGNING_URL` | Generate Embedded Signing URL | Generate a one-time URL for a human to sign one recipient action from a previously submitted request. The recipient must have been configured as an embedded SIGN action before submission; API submission requires a paid Zoho Sign plan and send credits. This action does not sign the document. Hand the URL to the intended signer immediately because it must be opened within two minutes and can be used only once. |
| `ZOHO_SIGN_GENERATE_REQUEST_EMBEDDED_SEND_URL` | Generate Request Embedded Send URL | Generate a short-lived, human-facing embedded editor URL for an owned active draft request. Open the URL within two minutes to start a one-hour session. This action only creates the handoff URL; it does not send the request. |
| `ZOHO_SIGN_GENERATE_TEMPLATE_EMBEDDED_SEND_URL` | Generate Template Embedded Send URL | Generate a short-lived embedded editor and sending URL for an owned Zoho Sign template. Open the URL within two minutes to start a one-hour human editing session. Generating the URL does not itself send a request; a completed send may require paid API entitlement and credits. |
| `ZOHO_SIGN_GET_ORGANIZATION` | Get Organization | Get the connected Zoho Sign organization, license label, administrative context, and relevant template, embedded-workflow, and signer-group feature flags. |
| `ZOHO_SIGN_GET_REQUEST` | Get Request | Get one request's status, documents, recipient actions, and signer fields. |
| `ZOHO_SIGN_GET_REQUEST_FIELD_DATA` | Get Request Field Data | Get recipient-entered field labels and values from a completed Zoho Sign request. Draft and in-progress requests do not have completed field data. |
| `ZOHO_SIGN_GET_REQUEST_REMINDER_SETTINGS` | Get Request Reminder Settings | Get automatic email reminder settings for an owned Zoho Sign request. |
| `ZOHO_SIGN_GET_TEMPLATE` | Get Template | Get one Zoho Sign template's documents, reusable recipient roles, signer fields, and prefill fields. |
| `ZOHO_SIGN_LIST_FIELD_TYPES` | List Field Types | List account-specific Zoho Sign field type IDs, names, categories, and mandatory defaults for use when placing signer fields. |
| `ZOHO_SIGN_LIST_FOLDERS` | List Folders | Return one controllable page of Zoho Sign folders. |
| `ZOHO_SIGN_LIST_MY_REQUESTS` | List My Requests | Return one controllable page of requests assigned to or pending for the connected Zoho Sign user. |
| `ZOHO_SIGN_LIST_REQUESTS` | List Requests | Return one controllable page of Zoho Sign document requests, optionally filtered by status and search columns. |
| `ZOHO_SIGN_LIST_REQUEST_TYPES` | List Request Types | Return one controllable page of Zoho Sign document request types. |
| `ZOHO_SIGN_LIST_SIGNER_GROUP_RECIPIENTS` | List Signer Group Recipients | Return one page of recipients for a Zoho Sign signer group. An empty result does not prove that the signer group exists. |
| `ZOHO_SIGN_LIST_SIGNER_GROUPS` | List Signer Groups | Return one controllable page of Zoho Sign signer groups, optionally filtered by group name. |
| `ZOHO_SIGN_LIST_TEMPLATES` | List Templates | Return one controllable page of reusable Zoho Sign templates. |
| `ZOHO_SIGN_LIST_USERS` | List Users | Return one controllable page of users in the connected Zoho Sign organization without email addresses or profile photos. |
| `ZOHO_SIGN_MARK_REQUEST_FOR_CORRECTION` | Mark Request For Correction | Move an owned in-progress request into correction mode before any signer completes. The request must have been submitted through a paid, credit-consuming API-send workflow. |
| `ZOHO_SIGN_MERGE_TEMPLATES_INTO_REQUEST` | Merge Templates Into Request | Merge at least two owned templates into an existing owned Zoho Sign draft request. This updates the draft but does not submit it or send it to recipients. |
| `ZOHO_SIGN_PREVIEW_TEMPLATE_MERGE` | Preview Template Merge | Preview whether two or more Zoho Sign templates are compatible for merging and retrieve the merged fields and recipient roles. This read-only preview does not create a request or send anything. |
| `ZOHO_SIGN_RECALL_REQUEST` | Recall Request | Irreversibly recall an owned sent Zoho Sign request and cancel its remaining signing process. Recipients can no longer view or sign the request after recall. The request must already have been submitted through the paid, credit-consuming API-send workflow. |
| `ZOHO_SIGN_REMIND_REQUEST_RECIPIENTS` | Remind Request Recipients | Immediately send a real reminder email to every pending recipient of an owned sent request. This externally visible action requires the paid API-send workflow, and repeated calls send additional email reminders. |
| `ZOHO_SIGN_SELF_SIGN_REQUEST` | Self Sign Request | Irreversibly apply the connected user's legal signature and complete an owned Zoho Sign self-sign request. The request must already be configured for self-signing and in a signable state. This requires an API-capable paid plan; confirm the request and field values before calling because signing cannot be undone. |
| `ZOHO_SIGN_SUBMIT_REQUEST` | Submit Request | Irreversibly send an owned Zoho Sign draft request to its recipients after applying final signer fields. This requires an API-capable paid plan and send credits; Zoho documents a cost of five credits per envelope submission. |
| `ZOHO_SIGN_UPDATE_REQUEST` | Update Request | Update an owned draft or correction-mode request, including settings, recipients, fields, and optional added files. This does not send the request. |
| `ZOHO_SIGN_UPDATE_REQUEST_TYPE` | Update Request Type | Update an existing Zoho Sign document request type's name and optionally its description. A replacement name is required even when changing the description. |
| `ZOHO_SIGN_UPDATE_SIGNER_GROUP` | Update Signer Group | Rename an owned Zoho Sign signer group, add recipients, and remove existing recipients by ID. |
| `ZOHO_SIGN_UPDATE_TEMPLATE` | Update Template | Update an owned Zoho Sign template's settings, reusable roles, signer fields, field removals, and optional added PDF documents. |

## Supported Triggers

None listed.

## Troubleshooting

### 1. Why does Claude not use the Composio connector for Zoho Sign?

The connector can show as connected, but Claude must use it in each Zoho Sign conversation.
- Click + at the lower left of the chat, or type /.
- Hover Connectors.
- Turn on Composio.
- Ask Claude to connect to Zoho Sign again.

### 2. Why does Claude show an MCP server error before Zoho Sign connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Zoho Sign.
- Check that the connector URL is https://connect.composio.dev/mcp.
- Connectors run from Anthropic's cloud, so your device network is usually not the problem.
- Add the connector again from Customize > Connectors, then ask Claude to connect Zoho Sign.
- If it fails again, send the error and the ofid_ reference id to support@composio.dev.

### 3. Why does the Zoho Sign authorization link not work?

The Composio connector is one server. Your Zoho Sign account connects separately when Claude asks for it.
- If the browser does not open, or the link expires, ask Claude to retry the Zoho Sign connection.
- Composio creates a fresh Zoho Sign authorization link.
- Open that link in your browser and finish the Zoho Sign sign-in.

### 4. Why do Zoho Sign actions fail after they worked before?

The Zoho Sign connection can expire or lose permission.
- Ask Claude to inspect the Zoho Sign connection.
- If the connection is unhealthy, disconnect it when Claude prompts you.
- Reconnect the Zoho Sign account and retry the action.
- If Claude shows a permission prompt, approve it before Claude changes data in Zoho Sign.
- If the action still fails with a permission error, check that the connected account has that permission in Zoho Sign itself.

### 5. How do I switch to a different Zoho Sign account?

Claude can manage the Zoho Sign connection for you.
- Ask Claude to disconnect or delete the current Zoho Sign account.
- Ask Claude to connect Zoho Sign again.
- Open the new Composio authorization link for Zoho Sign.
- Sign in with the other Zoho Sign account in the browser.
- After the account connects, ask Claude to retry the Zoho Sign task.

### 6. Why is my Zoho Sign connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Zoho Sign connection works in Claude Web, Desktop, and Cowork.
- In Claude Desktop, open Customize > Connectors.
- Next to Composio, click ⋮ and click Clear cache.
- If Zoho Sign tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
- On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Zoho Sign.

## Creating MCP Server - Stand-alone vs Composio SDK

The Zoho Sign MCP server connects Claude Web, Desktop, and Cowork to your Zoho Sign account through Composio. Once connected, Claude can use the available Zoho Sign tools and triggers to complete tasks on your behalf.

## Complete Code

None listed.

## How to build Zoho Sign MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/zoho_sign/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/zoho_sign/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/zoho_sign/framework/atomic-agent)

## Related Toolkits

- [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.
- [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.
- [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization.
- [ActiveMerge](https://composio.dev/toolkits/active_merge) - ActiveMerge is a document automation platform for generating documents, images, merged files, and e-signature workflows. It helps teams turn templates and stored files into finished, shareable documents faster.
- [Affinda](https://composio.dev/toolkits/affinda) - Affinda is an AI-powered document processing platform that automates data extraction from resumes, invoices, and more. It streamlines document-heavy workflows by turning files into structured, actionable data.
- [Agility cms](https://composio.dev/toolkits/agility_cms) - Agility CMS is a headless content management system for building and managing digital experiences across platforms. It lets teams update content quickly and deliver omnichannel experiences with ease.
- [Airparser](https://composio.dev/toolkits/airparser) - Airparser is an AI-powered parser for extracting structured data from emails, documents, PDFs, and files. It turns messy inbound content into clean fields your apps and workflows can use.
- [Algodocs](https://composio.dev/toolkits/algodocs) - Algodocs is an AI-powered platform that automates data extraction from business documents. It delivers fast, secure, and accurate processing without templates or manual training.
- [Api2pdf](https://composio.dev/toolkits/api2pdf) - Api2Pdf is a REST API for generating PDFs from HTML, URLs, and documents using powerful engines like wkhtmltopdf and Headless Chrome. It streamlines document conversion and automation for developers and businesses.
- [Apitemplate](https://composio.dev/toolkits/apitemplate_io) - Apitemplate is an API service for generating PDFs and images from reusable templates. It turns JSON data into branded documents and visuals without custom rendering code.
- [Archive.org](https://composio.dev/toolkits/archive_org) - Archive.org is the Internet Archive's digital library of websites, books, audio, video, and images. Use it to preserve, explore, and access historical web captures and public-domain media.
- [Aryn](https://composio.dev/toolkits/aryn) - Aryn is an AI-powered platform for parsing, extracting, and analyzing data from unstructured documents. Use it to automate document processing and unlock actionable insights from your files.
- [Boldsign](https://composio.dev/toolkits/boldsign) - Boldsign is a digital eSignature platform for sending, signing, and tracking documents online. Organizations use it to automate agreements and manage legally binding workflows efficiently.
- [Boloforms](https://composio.dev/toolkits/boloforms) - BoloForms is an eSignature platform built for small businesses, offering unlimited signatures, templates, and forms. It simplifies digital document signing and team collaboration at a predictable, fixed price.
- [Box](https://composio.dev/toolkits/box) - Box is a cloud content management and file sharing platform for businesses. It helps teams securely store, organize, and collaborate on files from anywhere.
- [Box MCP](https://composio.dev/toolkits/box_mcp) - Box MCP is Box's hosted MCP server that exposes enterprise files, folders, and metadata. It provides secure, centralized access to corporate content for search and management.
- [Carbone](https://composio.dev/toolkits/carbone) - Carbone is a blazing-fast report generator that turns JSON data into PDFs, Word docs, spreadsheets, and more using flexible templates. It lets you automate document creation at scale with minimal code.
- [Castingwords](https://composio.dev/toolkits/castingwords) - CastingWords is a transcription service specializing in human-powered, accurate transcripts via a simple API. Get seamless audio-to-text conversion for interviews, meetings, podcasts, and more.
- [CertSeal](https://composio.dev/toolkits/cert_seal) - CertSeal is an API platform for issuing and managing verifiable digital certificates. Use it to automate trusted certificate workflows for recipients, batches, designs, and webhooks.
- [Cloudconvert](https://composio.dev/toolkits/cloudconvert) - CloudConvert is a powerful file conversion service supporting over 200 file formats. It streamlines converting, compressing, and managing documents, media, and more, all in one place.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Zoho Sign MCP?

With a standalone Zoho Sign MCP server, the agents and LLMs can only access a fixed set of Zoho Sign tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Zoho Sign and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Claude Cowork?

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Zoho Sign tools.

### Can I manage the permissions and scopes for Zoho Sign while using Tool Router?

Yes, absolutely. You can configure which Zoho Sign scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Zoho Sign data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
