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 provides electronic signature workflows for creating, sending, tracking, and managing documents, templates, recipients, and account resources.
Create a persistent Zoho Sign folder. Zoho Sign provides no folder-delete API endpoint, so this action cannot automatically clean up the folder.
Upload 1-40 PDF documents and create a Zoho Sign draft request. This action does not send the request to recipients.
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.
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.
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.
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.
Upload 1-40 PDF documents and create a reusable Zoho Sign template with recipient roles and signer fields.
Permanently delete one document file from an owned Zoho Sign request. This destructive action cannot be undone and does not delete the whole 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.
Destructively move an owned reusable Zoho Sign template to trash. This is a soft delete rather than immediate permanent erasure.
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.
Download one PDF document from a Zoho Sign request.
Download all documents in a Zoho Sign request as a PDF or ZIP, optionally merged and including the completion certificate.
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.
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.
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.
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.
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.
Get the connected Zoho Sign organization, license label, administrative context, and relevant template, embedded-workflow, and signer-group feature flags.
Get one request's status, documents, recipient actions, and signer fields.
Get recipient-entered field labels and values from a completed Zoho Sign request. Draft and in-progress requests do not have completed field data.
Get automatic email reminder settings for an owned Zoho Sign request.
Get one Zoho Sign template's documents, reusable recipient roles, signer fields, and prefill fields.
List account-specific Zoho Sign field type IDs, names, categories, and mandatory defaults for use when placing signer fields.
Return one controllable page of Zoho Sign folders.
Return one controllable page of requests assigned to or pending for the connected Zoho Sign user.
Return one controllable page of Zoho Sign document request types.
Return one controllable page of Zoho Sign document requests, optionally filtered by status and search columns.
Return one page of recipients for a Zoho Sign signer group. An empty result does not prove that the signer group exists.
Return one controllable page of Zoho Sign signer groups, optionally filtered by group name.
Return one controllable page of reusable Zoho Sign templates.
Return one controllable page of users in the connected Zoho Sign organization without email addresses or profile photos.
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.
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.
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.
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.
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.
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.
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.
Update an owned draft or correction-mode request, including settings, recipients, fields, and optional added files. This does not send the request.
Rename or change the description of an existing Zoho Sign document request type.
Rename an owned Zoho Sign signer group, add recipients, and remove existing recipients by ID.
Update an owned Zoho Sign template's settings, reusable roles, signer fields, field removals, and optional added PDF documents.
The Zoho Sign integration connects your Dench AI CRM directly to Zoho Sign, so agents can read and act on your Zoho Sign data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
43 actions are available for agents to invoke on your behalf. Every call runs through Zoho Sign's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Zoho Sign and click Connect — you'll authorize access through Zoho Sign's own sign-in flow. No API keys or code required.
Ask an agent to use Zoho Sign in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Zoho Sign integration connects your AI CRM to Zoho Sign, so AI agents can work with your Zoho Sign data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Zoho Sign integration currently exposes 43 actions, including Create Folder, Create Request, Create Request From Merged Templates, Create Request From Template, Create Request Type, and Create Signer Group. Agents invoke them on your behalf from chat or from automations.
No. You connect Zoho Sign from your Dench workspace using Zoho Sign's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Zoho Sign's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Zoho Sign connection from your workspace settings at any time.