Zoho Sign
DocumentsAutomate e-signature workflows in Zoho Sign. Agents send documents for signing, launch requests from reusable templates, remind stalled signers, recall documents sent in error, and download the completed signed PDF into FlowRunner storage.
What This Integration Enables
Zoho Sign's API has a feature most e-signature automation quietly lacks: a real draft state. Create Document and Send From Template both accept Send Immediately as false, which means a workflow can fully assemble a signature request, document, recipients, signing order, and stop, holding it for review before a single notification fires. That is human-in-the-loop as an API primitive, and this connector is built around it. FlowRunner agents prepare requests from files or templates, hold them for approval, submit on sign-off, chase stalled signers, recall mistakes, and archive every completed PDF into FlowRunner storage. For teams on the Zoho suite, this closes the loop between where deals happen and where agreements get signed, without anyone shepherding paper: - Templates carry the approved language; agents only ever map roles to real recipients via action_ids - Draft-then-submit puts a person between assembly and notification on consequential paper - Reminders run on schedule against actual signer status, not on someone remembering to nudge - Recall removes a mistaken request from recipients' queues while retaining it for records - Completed PDFs archive automatically with public URLs your other systems can store and audit The two operations that stay with people, submitting and recalling, are exactly the two that change what a counterparty sees, and FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) layer holds both.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The closed deal whose contract was waiting for one click
A [HubSpot](/integrations/hubspot) deal moves to closed-won. The agent reads the standard agreement's roles with Get Template, maps the deal contact and the company signer, and creates the request as a draft. The deal owner gets the draft link, checks the entity name and term, and approves. Submit Document fires, reminders run automatically, and when the last signature lands, Download Signed PDF archives the executed copy and writes its URL back to the deal. The owner's total effort: one review, one click, which is the correct amount.
The intake agreement that chases itself
A [Typeform](/integrations/typeform) submission kicks off a tailored agreement via Create Document, built from the respondent's answers. The agent polls Get Document for signer status and runs Remind Document on a schedule until completion, backing off after each nudge. Stalled requests past the window escalate to [Slack](/integrations/slack) with the recipient's status, so a person decides whether to call, resend, or drop. Nobody keeps a spreadsheet of who has not signed, because the workflow is the spreadsheet.
The signature pipeline on one pane
Each morning the agent pages through List Documents by status: in progress, completed, declined, recalled. In-progress requests older than the SLA get flagged with days outstanding; completions from yesterday get their Download Signed PDF URLs logged to [Google Sheets](/integrations/google-sheets) next to their deal references; declines post to the owner immediately. Legal and ops read one live sheet instead of asking each other what is still out for signature.
Human-in-Loop Highlight
Recall Document cannot be undone: it voids an in-progress signature request, removes it from every recipient's queue, and any signatures already collected on it are finished business. Recalling the wrong document kills a live deal's paperwork mid-signature and tells every counterparty the company changed its mind. So recall in FlowRunner is a proposal with evidence: the agent presents the request's status from Get Document, who has signed, who is pending, and why it flagged the request, and a person confirms the void. The submit side gets the mirrored treatment, using Zoho Sign's own draft state: consequential documents are created with Send Immediately off, and Submit Document fires only on the owner's approval, because notifying a counterparty to sign is a commitment the company should make on purpose. Assembly, chasing, monitoring, and archiving run at machine speed between those two human decisions.
Agent Capabilities
10 actionsDocuments
7- List Documents Retrieves a paginated list of signature requests (documents) in your Zoho Sign account. You can filter by status - for example draft, in progress, completed, declined, or recalled - and page through large lists using the returned cursor.
- Get Document Retrieves the full details of a single signature request (document) by its request ID, including its status, the recipient actions and their signing progress, document IDs, and timestamps.
- Create Document Creates a signature request from a file and sends it for signing in one step. Provide a publicly reachable URL to the source document (PDF, DOCX, and similar) and a list of recipients, each with an email, name, and signing order. By default the request is submitted immediately so recipients are notified; set Send Immediately to false to leave it as a draft you can review and submit later. Each recipient is added as a SIGN action unless you choose a different action type.
- Submit Document Submits a draft signature request so it is sent out and recipients are notified to act on it. Use this after creating a document with Send Immediately turned off, or whenever a request is still in draft state.
- Remind Document Sends a reminder email to the recipients of a signature request who have not yet completed their action. Useful for nudging signers on documents that are still in progress.
- Recall Document Recalls (voids) an in-progress signature request so it can no longer be acted on by recipients. Recalled documents are retained for record-keeping but are removed from recipients' pending queues. This action cannot be undone.
- Download Signed PDF Downloads the signed PDF for a completed signature request and stores it in FlowRunner file storage, returning a public URL. Use this to archive or forward the finalized, signed document in later steps of your flow. The document must be completed (fully signed) for the signed PDF to be available.
Templates
3- List Templates Retrieves a paginated list of templates in your Zoho Sign account. Templates are reusable documents with predefined fields and recipient roles that can be used to send new signature requests quickly. Page through large lists using the returned cursor.
- Get Template Retrieves the full details of a single template by its template ID, including its document IDs and the recipient roles (actions) defined on it. Inspect this to learn which roles need recipient emails and names before sending a document from the template.
- Send From Template Creates and sends a new signature request from an existing template. Map each template role (action) to a real recipient by supplying the action_id (from Get Template), the recipient's email, and name. By default the request is submitted immediately so recipients are notified; set Send Immediately to false to leave it as a draft.
Frequently Asked Questions
What can FlowRunner do with Zoho Sign?
FlowRunner agents can run List Documents, Get Document, and Create Document in Zoho Sign, plus 7 more actions.
Does connecting Zoho Sign to FlowRunner require OAuth?
Yes. Zoho Sign connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Zoho Sign trigger a FlowRunner workflow automatically?
Zoho Sign doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Zoho Sign
$100 in credits. No card required. Connect in minutes.