--- title: "Zoho Writer Integration" description: "Zoho Writer is the word processor of the Zoho suite, and its API centers on mail merge. Agents merge a template with records to produce documents one by one or in batch, store them in WorkDrive, send them for signature through Zoho Sign, or generate fill-in links." url: https://flowrunner.ai/integrations/zoho-writer date_modified: 2026-09-04T14:07:24-07:00 --- # Zoho Writer [Documents](https://flowrunner.ai/integrations/category/documents-forms) Zoho Writer is the word processor of the Zoho suite, and its API centers on mail merge. Agents merge a template with records to produce documents one by one or in batch, store them in WorkDrive, send them for signature through Zoho Sign, or generate fill-in links. 13 actions · OAuth · available [Zoho Writer website](https://www.zoho.com/) · [Platform Documentation](https://www.zoho.com/writer/) · Capability data verified 2026-08-13 1. A renewal batch falls due and every customer needs their own agreement 2. Agent reads each customer's terms, dates, and pricing from the source records 3. Get Document Fields returns the exact merge field names the template defines, so the payload uses the template's keys rather than the flow's 4. Merge And Invoke merges the batch and returns the documents as links, which is the route that holds up at volume 5. A sample from the batch is reconciled against its source record before anything is delivered 6. The renewals owner receives the sample and the proposed recipient list for the signature step 7. The renewals owner names the signature recipients explicitly, and Merge And Sign runs only against that named list ## What This Integration Enables Zoho Writer's API is not shaped like a document generator. It is shaped like a set of destinations. The merge itself is the same operation every time: a Writer template plus your data. What differs is where the result goes, and the connector exposes that as seven distinct merge actions rather than one action with a delivery parameter. Merge Document hands the file back. Merge And Store files it into [Zoho WorkDrive](https://flowrunner.ai/integrations/zoho-workdrive). Merge And Sign sends it through [Zoho Sign](https://flowrunner.ai/integrations/zoho-sign). Merge And Deliver Via Webhook posts it to an endpoint of your own, one per record as each completes. Merge And Invoke returns links rather than files, which is the route a large batch survives on. Merge And Share Fillable Link returns something the recipient finishes themselves. Merge With Presets uses the settings the template owner already saved in Writer, so the flow supplies only the data. Two structural facts shape the design. There is no create or delete document operation here, because the version 1 reference publishes none, which means the template is authored by a person in Writer and the flow supplies data and destination rather than owning the document's life. And your Zoho account lives in exactly one datacenter, with both the API host and the OAuth host following it, across the United States, Europe, India, Australia, Japan, Canada, China, and Saudi Arabia. For an operations team already inside the Zoho suite, that regional pinning is often the reason this connector is the right one rather than a general purpose generator. Merge And Sign emails real people a document to sign, which is why [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) belongs specifically in front of that destination rather than in front of the merge. ### Without FlowRunner **The merge and the destination are separate problems**: A document is generated, then somebody works out where to file it, who to send it to, and how **Field names are guessed from the template's appearance**: A merge fills half the document because the placeholder was named differently from the CRM field **Batch merges are the same call, repeated**: A hundred records means a hundred calls, and the hundredth fails on a throttle limit nobody planned for ### With FlowRunner **The destination is the operation**: One call merges and files it in WorkDrive, or sends it for signature, or posts it to your endpoint, or returns a fillable link **Field names are read from the template**: The flow asks the template which merge fields it defines and builds the payload against those exact keys **Batches are merged as batches**: One call merges the whole set and returns links, with each record its own document or all of them combined ## Use Case Scenarios ### One template, several destinations, chosen by audience A single agreement template serves three situations, and the flow picks the destination rather than post processing the file. A deal closing in [Zoho CRM](https://flowrunner.ai/integrations/zoho-crm) merges by record id, so Zoho fetches the data itself, and goes straight to Merge And Sign. An internal record that only needs filing goes through Merge And Store into the client folder in WorkDrive, optionally replacing last quarter's version. A customer who still has to supply their own details gets Merge And Share Fillable Link, which hands them a partly filled document to complete rather than a form to retype from. The same template, the same merge data, three different endings. ### A batch that survives its own size Month end produces several hundred statements. Merge Document one record at a time is the obvious approach and the one that meets Zoho's throttle limits first. Instead the agent calls Merge And Invoke, which merges the whole batch and returns the documents as links, with each record becoming its own document and the filename itself built from merge fields so the results are addressable afterward. Combine PDFs assembles the ones destined for a single recipient into a pack, and Combine And Store PDFs files the archive copy into WorkDrive without it passing through the flow at all. A summary of the run lands in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and the exceptions post to [Slack](https://flowrunner.ai/integrations/slack). ### The signature step that names its own recipients Renewals are the case where the connector's convenience becomes a hazard. Merge And Sign will accept an empty signer list, and an empty list does not mean nobody: it means whoever the template itself defines, which may be a real recipient configured months ago by somebody who has since moved teams. So the renewal agent never sends with an empty list. It resolves each signer from the customer record, builds the recipients explicitly with the act each performs and the language they are notified in, and puts that list in front of a person before the batch runs. Recipients can be notified by SMS or WhatsApp as well as email and in their own language, which is worth getting right on purpose rather than by inheritance. ## Human-in-Loop Highlight Merge And Sign has a default that a flow cannot inspect. Leave the signers empty and Zoho uses whatever recipients the template itself defines, and this connector offers no operation that reads them back: Get Document Fields returns merge fields, not signature recipients. So a flow that merges a hundred renewal agreements with an empty signer list is dispatching a hundred signature requests to a list it structurally cannot see, and the first evidence of who received them arrives from the recipients. That is why the renewals agent stops and asks for the list rather than inheriting one: "Renewal batch, 118 agreements, template Annual Services Agreement 2026. Signers resolved from the customer records: 118 primary signers, 14 with a second approver, 6 records with no signing contact on file. Sending with these named recipients, or hold the 6 and send 112?" The operations owner answers in a sentence. The agent merged, reconciled, and found the six gaps. What it refused to do was let an empty field decide who gets asked to sign a contract. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 13 actions ### Documents 3 - **List Documents** Lists documents in the Zoho Writer account, or narrows to the templates of one kind: merge templates, sign templates, or fillable templates. Paged, and sortable by name or by creation or modification time. - **Get Document Fields** Returns every merge field defined in a template, which are the exact keys the merge operations expect. Read this before building a merge rather than guessing the field names. - **Download Document** Downloads a Writer document into FlowRunner file storage and returns the stored file URL. ### Merge 7 - **Merge Document** Fills a template with your data and returns the merged document. The merge data is given in exactly one of six ways: an object, CSV or JSON content, a CSV or JSON URL, or a record id for a Zoho CRM, Creator, or Bigin template. The result can be password protected, with copying, printing, editing, or filling restricted. - **Merge And Store** Fills a template and stores the merged document straight into a Zoho WorkDrive folder rather than returning it, optionally overwriting an existing file there. Zoho marks this version 1 route as heading for deprecation, so treat it as working but time limited. - **Merge And Sign** Fills a template and sends the merged document for signature through Zoho Sign. Recipients can be asked to sign, approve, view, or sign in person, and each can be notified in their own language and by SMS or WhatsApp as well as email. Leaving the recipients empty uses whatever the template defines, which is the behavior this page's human gate exists for. - **Merge And Deliver Via Webhook** Fills a template and posts the merged documents to a URL of your own instead of returning them, either one per record as each is merged or all together once the whole merge completes. The URL travels inside the request, so nothing is registered and nothing is left behind to manage. - **Merge And Invoke** Fills a template and returns the merged documents as links rather than as files, which is the route to use for a large batch. Every record can become its own document or all of them can be merged into one, and the filename may itself contain merge fields. - **Merge And Share Fillable Link** Fills a template and returns a link the recipient opens to complete the remaining fields themselves, rather than producing a finished document. - **Merge With Presets** Fills a template using the merge settings already saved on it in Zoho Writer, instead of spelling out the output and delivery settings on every call. Use it when the template owner has configured the merge in the Writer interface and the flow only supplies the data. ### PDF Tools 3 - **Combine PDFs** Combines several PDFs into one and stores the result in FlowRunner file storage. - **Combine And Store PDFs** Combines several PDFs into one and stores the result in a Zoho WorkDrive folder rather than returning it, so an archive copy never has to pass through the flow. - **Combine And Deliver PDFs Via Webhook** Combines several PDFs into one and posts the result to a URL of your own. As with the merge webhook, the URL is carried inside the request and no subscription is registered. ## Frequently Asked Questions ### What can FlowRunner do with Zoho Writer? FlowRunner agents can run List Documents, Get Document Fields, and Download Document in Zoho Writer, plus 10 more actions. ### Does connecting Zoho Writer to FlowRunner require OAuth? Yes. Zoho Writer connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Zoho Writer trigger a FlowRunner workflow automatically? Zoho Writer doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Zoho Writer?** This integration exposes Zoho Writer to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/zoho-writer. Site index: https://flowrunner.ai/llms.txt