Article

Create client welcome PDFs with Zoho Writer mail merge

For solo consultants, turn approved spreadsheet records into separate welcome PDFs, check free-plan limits and review every file before sending.

Editorial illustration for Create client welcome PDFs with Zoho Writer mail merge: a document represents the research briefing. Not documentary evidence.

As of 19 November 2026, Zoho Writer’s documented free automation can turn approved spreadsheet records into separate client welcome PDFs, provided your account’s allowances cover the work. Keep copying your existing Google Doc if that routine is manageable; consider mail merge when repeated field entry warrants maintaining a template and an export file. Zoho’s merge workflow inserts stored values into a reusable document—no AI subscription is needed.

Consider an illustrative solo US design consultant who is comfortable with documents and spreadsheets, but not coding. The owner already has permitted Google Docs and Sheets access, an approved welcome-document master, and needs 30 new PDFs a month, with no more than five on any day.

The budget is US$0 for additional software subscriptions, excluding existing subscriptions, equipment, connectivity and labour. This is a planning example, not a customer case. The goal is one reviewed welcome PDF per client, not a contract, signature request or automatically sent email.

When is copying your Google Doc enough?

Stay with manual copies if each document is easy to prepare and check. Consider Writer if the same approved details recur throughout each welcome pack and you can maintain a reliable source list. Before switching, weigh repetition, the busiest day’s workload, correction effort, storage needs and template upkeep—not just the monthly document count.

For the manual route, leave the approved master unchanged. Use File > Make a copy, name the client’s copy, replace its variable details, then download a PDF and inspect it. Google documents copying and downloading files. The zero-additional-subscription assumption depends on your existing permitted access; it does not mean every business Google account is free.

Option and best fit

Additional software cost

Capacity to check

Output handling

Ongoing work

Existing Google Docs: manageable individual preparation

US$0 under the existing-account assumption

No merge allowance assumed

Edit and download each copy

Repeated entry and final review

Writer free automation: recurring fields justify setup

US$0 with eligible WorkDrive Individual

200 credits/month; 10 merges/day per organization

Separate PDFs; My Folder restriction

Template, CSV exports and completion record

Writer paid automation: a verified capacity shortfall

Flexible: US$1/month plus usage; Fixed: from US$25/month. Before tax.

Confirm the actual paid account’s limits

Check storage entitlement separately

Same review work, plus billing management

Automation changes where you do the work: maintain a shared template instead of editing every repeated field. It does not establish that the finished document is correct, or that the change will save your business time.

Will the free plan fit your workload?

As of 19 November 2026, WorkDrive Individual is a continuing free plan with 5 GB of storage and built-in Writer, Sheet and Show. That is different from a temporary business-plan trial, and storage capacity is separate from document-generation capacity.

Zoho’s allowance table lists 200 monthly automation credits and 10 daily merges per organization for WorkDrive Individual/Essential. Ordinary PDFs cost one credit per input record; fillable PDF forms cost five. Combining records does not reduce that consumption, and extra output formats can add charges. Free credits do not roll over.

Illustrative calculation using those limits: 30 records × 1 credit = 30 credits, or 15% of the monthly allowance, before tests, corrections and other account usage. Five new records a day fit; all 30 on one day do not. At five a day, the work spans six days.

Check remaining usage under User Profile > Admin Panel > Usage Report. Zoho’s usage rules say daily limits reset at midnight in the applicable data centre. Do not substitute the documentation’s larger general interface ceilings for your plan’s lower limit.

There is also a destination constraint: as checked on 19 November, Free Individual merges save to My Folder; you cannot change the save location during the merge. Plan to organize reviewed files manually, not automatically route them into client-specific team folders.

What should you prepare before uploading client records?

Use an account you control for the business and confirm you are authorized to upload the necessary client information. Zoho’s terms permit business use but require rights to uploaded information, prohibit shared user licences and give service-specific terms precedence.

For this workflow, a small staging sheet is easier to inspect than exporting an entire client database. The following columns are a suggested record design, not mandatory Zoho field names:

  • ClientID: a stable identifier that distinguishes clients with similar names.

  • ClientName and ProjectName: the approved wording to appear in the welcome document.

  • ApprovedStartDate: the agreed date, with an unambiguous display format.

  • Ready: a text value of Yes only for records approved for this batch.

  • Only the contact details the document actually needs. Leave out payment data, passwords and unrelated notes.

Keep one header row and one client per row. Download the prepared sheet as a dated CSV—a plain-text file of spreadsheet values. Google supports CSV downloads from Sheets. Inspect the exported file itself: verify IDs, dates and included rows rather than assuming spreadsheet formatting or hidden-row choices carried over.

Writer accepts CSV files and one data source per template. This guide uses an exported snapshot, not a live Google Sheets connection. Later changes in Sheets will need a fresh export for this workflow; there is no automatic completion write-back in these steps.

If the problem is gathering those details in the first place, that is an earlier task. The customer-enquiry forms comparison covers collecting requests and assigning follow-up, before preparing an approved welcome pack.

How do you build the reusable welcome template?

Keep the welcome wording fixed and approved; use fields only where client details should vary. Zoho documents this setup sequence:

  1. Create a template through File > New Automation Template > Merge Template. Alternatively, open an existing Writer document and use Automate > Convert to merge template.

  2. Open Automate > Configure and select the prepared CSV as the data source.

  3. Insert the matching merge fields where each client value belongs. Set field types deliberately, especially dates, and retain the approved fixed wording.

  4. Choose manual execution so you decide when each batch runs.

For an agreed project start date, use ApprovedStartDate from the record—not a field that changes to today’s date. Keep the original editable master independently available, and give each substantive template revision a version you can record against its outputs.

How do you select only the intended clients?

Under Select Data Source, open the Filter control. Choose your Ready field, an equality condition and the text value Yes. Zoho’s filtering instructions explain that case and trailing spaces matter: Yes, yes and Yes followed by a space are different. A checkbox may contain true/false rather than text, so do not mix the two designs.

Check the selected client IDs against the intended batch. A Ready flag is your selection convention, not proof of client approval or a record that a PDF has already been produced. Keep completion status separately, and remove completed records from subsequent export batches unless a correction is intentional.

Before generation, use Preview Merge and move through every selected record, as Zoho describes. Check that the displayed values and layout match the approved source; a preview alone is not the final acceptance check.

How do you create one PDF per client?

Following Zoho’s output instructions, choose Merge & Store in the output settings, then Create separate documents and the ordinary PDF format. Do not choose combined output: that puts multiple clients into one file instead of creating the intended individual deliverables.

Use merge fields in filenames to distinguish clients. A suggested pattern is Welcome_ClientID_ProjectName_v1, using a short project label and a deliberate version suffix. Avoid unnecessary personal details in filenames, and distinguish corrected versions rather than assuming repeated names will be handled safely.

Before your first real batch, generate dummy records within your available allowance. Include a long name, a long project title, a leading-zero ID, an unambiguous date and a missing required value. Also try No, blank and a trailing-space Ready value. These are suggested checks to perform, not reported test results.

Once the selection and preview are right, run the merge manually. Keep client delivery separate: generate, inspect and approve the PDFs before choosing who receives them.

What must you check before sending or rerunning?

Start with the actual files and the job log. In the template, open Automate > Finish > View Log. Zoho’s logs distinguish successful or failed record merges from successful or failed output processing, with record-level details. A completed merge is not itself content approval.

Open every final PDF. Use these acceptance checks:

  • The intended client IDs match the separate files produced, with no missing or unexpected client.

  • Names, project details, approved dates and commitments match the source record and approved master.

  • Required fields are populated; long text, page breaks and formatting remain readable.

  • Each file contains only that client’s information.

  • The approved file is in the intended restricted location, and any recipient access is correct.

If a batch is only partly successful, reconcile the log with existing output files before trying again. Identify the records that genuinely need another output, correct the source or template, and prepare a smaller batch. Do not assume the same filename prevents duplicates or that every failed attempt is automatically refunded.

Manually record each client ID, approved file location, CSV snapshot, template version and review status in the authoritative spreadsheet. Record delivery separately. For later work, export fresh inputs from that updated record; reusing an old CSV can reselect clients you have already completed.

If the next step requires a signed agreement, use a signing workflow rather than treating this PDF as one. The Google eSignature and Zoho Sign comparison addresses that separate decision.

What should you retain, and when is paying worthwhile?

Keep restricted independent copies of the approved master, source snapshots, completion record and final documents. Writer supports formats including DOCX and PDF, but editable-file export should not be treated as a guarantee that another editor will preserve your merge configuration.

Uploading a client CSV entrusts its information to Zoho for processing; it no longer exists only in Google or on your computer. Zoho’s privacy policy recognizes customer ownership of service data and access, export and deletion-request rights. Deletion is not necessarily immediate across backups, and those provisions do not establish that every client-data use is permitted. Keep the upload minimal and access restricted.

Paid automation is unnecessary for the illustrative schedule if the available free allowances suffice. Consider it only after identifying a real capacity shortfall. As checked on 19 November 2026:

  • Monthly Flexible activation costs US$1, with consumed additional credits billed separately. Extra-credit charges require an add-on and exhausted free credits.

  • The USD pricing page lists US$0.05 per credit for the first 4,000 additional credits, with local taxes extra.

  • Fixed starts at US$25 per month for 500 additional credits.

For illustration, if 100 credits are actually chargeable after your account’s confirmed free allowance, monthly Flexible billing would be US$1 + (100 × US$0.05) = US$6 before tax. This is not the bill for the 30-PDF example, nor a claim about the free allowance after upgrading.

Confirm currency, included allowance, daily capacity and the full checkout price before purchasing. Do not infer team-folder rights from buying automation credits. Higher-volume pricing also needs a fresh check: the pricing page and billing help page describe the upper bands differently.

Check renewal terms too. Zoho’s general terms provide for automatic renewal and at least seven days’ notice of non-renewal; check the applicable order and service terms. A temporary trial is not the continuing free route, and trial data should be exported before expiry if you are not purchasing the relevant subscription.

Start with the smallest useful batch and compare the upkeep with your existing copying routine. Continue with Writer only if maintaining the template, exports and completion record makes sense for your work. Whether you choose automation or manual copies, the finish line is the same: a correct, individually reviewed welcome PDF, followed by a separate decision to send it.