How to Set Up Mail Merge and Document Automation in Zoho CRM

Sending a proposal or contract out for signature usually means pulling data from your CRM by hand. You paste it into a Word/Writer document, then repeat the process for every deal that closes. Zoho CRM’s mail merge and document automation tools eliminate that step entirely. You can generate a fully populated document straight from a deal, lead, or any other record, complete with tables of line items.

This guide walks through building a mail merge template from scratch. It covers merging in data from a record and its related modules. You’ll also insert a repeating table for sub-form data and send the finished document out through Zoho Sign. It also covers how to automate the entire workflow into a single button click, the same way Zenatta sets it up for its own clients.

Watch: Mail Merge Tutorial for Zoho CRM

What is Mail Merge in Zoho CRM?

Mail merge in Zoho CRM lets you take a record, such as a deal or a lead, and generate a document from it. A couple of button clicks pull that record’s data into a document you populate ahead of time. Instead of manually copying a client’s name, budget, and line items into a Word document, you build a template once. From there, you can run the merge against any record in that module whenever you need a new document.

This is most commonly used from the Deals module to produce a contract or proposal. The finished document typically goes out to a client for signature, but the same mechanics apply to any module.

Preparing Your Data

Before building a template, look at what data actually lives on the record you plan to merge from. A typical Deal record might include top-level fields like proposal dates and discovery notes. It may also include a sub-form, a table of related data such as a list of chosen add-ons with categories and quantities. Knowing which fields sit at the top level versus inside a sub-form matters. Zoho CRM treats each one differently when you build the template.

Creating a Mail Merge Template

If you open the three-dot menu on a record and click Mail Merge before any templates exist, you will see an empty list. Templates are not created from the record itself. They are created in Setup, under Templates, then Mailmerge.

From there, name the template, for example Proposal for Engagement. Choose the module it should run against, such as Deals. Choosing the correct module up front matters, since it determines which fields, including fields from related modules, will be available to merge later. Getting this wrong means the template will not have access to the data you actually need.

Once created, the template opens in an editor comparable to Microsoft Word or Google Docs. Standard text formatting controls run along the top for headings, alignment, and styling. Build out the static parts of the document, headings, labels, and boilerplate text, the same way you would in any word processor.

Merging Fields from Related Modules

The Automate panel on the right side of the template editor lists every field available to merge. You can reopen it any time via Automate, then Configure. This includes fields from the module the template was built against. It also includes fields from any related module, such as the linked Account and Contact on a Deal.

For a field like a contact’s name, you have a choice. You can pull it from the Deal module’s lookup field, or pull it directly from the Contacts module. Pulling directly from the related module is the more reliable approach. A Deal reliably has exactly one related Account and one related Contact, which lets Zoho CRM confidently retrieve the correct name every time.

Beyond names, any top-level field on the Deal can be inserted the same way, such as a budget figure or a required completion date. It will populate automatically whenever the merge runs.

Adding Sub-Form Data as a Repeating Table

Sub-form data, like a table of chosen add-ons, does not show up as a normal field in the Automate panel. It is not a single value; it is a table of rows. Zoho CRM handles this through repeat structures, and there are two kinds of repeating data you can merge in:

• A sub-form that lives directly inside the record, such as line items on a quote or add-ons attached to a deal.
• Related records from a completely separate module, such as a list of open activities connected to the record.

To insert a sub-form as a table, select it in the Automate panel and choose a repeat structure. Zoho CRM offers three options:

• Simple repeat: rows without a header row, rarely used in practice.
• Table for row repeats: the most common option, producing a table with a header row and one repeating row per sub-form entry, similar to line items on a quote.
• Table for column repeats: turns each sub-form row into a column instead of a row.

After inserting a table for row repeats, the editor marks the repeating row with a colored border. The row above it holds your column labels. These labels can use whatever terminology makes sense to the client, even if it differs from the internal field name in Zoho CRM. Inside the repeating row itself, map each column to a specific sub-form field, for example category, quantity, and notes.

Running the Merge from a Record

With the template built, open the target record, click the three-dot menu, and select Mail Merge. Choose the template you created and click Merge. Zoho CRM pulls the record’s data and retrieves the related sub-form rows. It generates the merged document and opens it in a Writer-style editor in a new tab, fully populated with real values from the record.

At this stage, you can also make one-off additions to the generated document, such as typing in a purchase order number the client requested. This does not affect the underlying template. Only clicking Update Template pushes a change into every future document created from that template going forward. If an edit needs to happen often, it is usually better to create a separate template rather than repeatedly hand-editing individual documents.

Reviewing and Distributing the Document

Once a document is merged, the icon in the top right, labeled Compose by default, switches to Distribute. From here you have several options for what happens next:

Option	What It Does	When to Use It
Merge and send as a new document	Creates the document and opens it for review before anything is sent.	Best default choice, since it lets you catch mistakes, like an incorrect contact, before distribution.
Merge and store	Saves the generated document directly into a location such as a WorkDrive folder referenced by a field on the record.	Good for automatic archiving without a manual download step.
Send for signature	Routes the document straight into Zoho Sign without a manual review step.	Best reserved for fully automated workflows, once you trust the data is correct every time.

Reviewing before sending matters in practice. Every so often, a merge goes out to the wrong contact at the account. That is easy to fix: swap the value and re-run the merge before anything goes out. From the review screen, you can also download the document as a DOCX file if a client wants to redline it before signing.

Setting Up Signer Fields for Zoho Sign

To send a document for signature, it needs signer fields built into it first. You can add these at the template level, so every document generated from that template already has them in place.

Inside the template editor, use the signer fields panel to add each signing party, for example the client and Zenatta as the two signers. Drag each signer’s fields, typically a signature field and a date field, directly into the document body wherever they should appear.

Once configured, running Send for Sign on a merged document routes it into Zoho Sign. It is automatically loaded and sent out to the first recipient in the signing order you defined.

Automating the Entire Process

The manual workflow works well, but it involves a fair number of clicks. You mail merge, select a template, merge now, send for sign, enter an email address, then send. For teams that send the same type of document repeatedly, that entire sequence can be wrapped into a custom function behind a single button.

Zenatta uses exactly this approach internally. A Send Proposal button on the Deal record grabs the template ID and the record ID, then retrieves the related contact. It sets that contact as the signer and sends the document out through Zoho Sign automatically. The mail merge and signature mechanics stay the same; the custom function just chains the steps together so a rep only has to click once.

Best Practices

• Build the template against the right module: this determines which related fields are available later, and it is much harder to fix after the fact.
• Pull related data from its source module: retrieve contact and account fields directly from the Contacts and Accounts modules rather than through Deal lookup fields.
• Standardize instead of hand-editing: if a one-off change happens often, create a dedicated template rather than repeatedly editing individual merged documents.
• Review before you send: use Merge and Send as a New Document so you can confirm the right contact and data before it goes out.
• Automate repetitive sends: once a workflow is proven manually, wrap it in a custom function to reduce clicks and reduce the chance of sending to the wrong recipient.

Common Mistakes to Avoid

• Building the template against the wrong module, which limits which related fields are available to merge.
• Triggering merges from inside the template editor instead of from the record’s own three-dot menu.
• Clicking Update Template for a one-off edit that was only meant to apply to a single document.
• Skipping the review step and sending straight to signature before verifying the correct contact and data.
• Forgetting to add signer fields to the template before attempting to send a document through Zoho Sign.
• Not accounting for pop-up blockers, which frequently interrupt the multiple new tabs the merge and sign process opens.

Frequently Asked Questions