Mail Merge template in Make
The Mail Merge family is a Make Generate Document Single option that fills a classic Word mail-merge template, using MERGEFIELD tags, with your data and outputs a PDF or Word document. It is the fastest path to migrate an existing Microsoft Word mail-merge letter into an automated, code-free Make scenario.
Before You Start
simple_mail_merge_template.docx uses standard Word mail-merge fields. Each merge field name maps to a key in your data file.sample_mail_merge_data.json (recommended), test.xml, or test.csv. The merge field names match the data keys.Sample File Pack
Download the files below. One mail merge template plus matching data in JSON, XML, and CSV.
Target configuration: Word mail-merge template + JSON in Document Data Text + PDF output.
What is the Mail Merge template template in Make?
The Mail Merge family reads a Word .docx built with classic MERGEFIELD tags and replaces each field with a value from your data. Because it is a .docx, you select PDF4me Word Template as the Template File Type in Make. Choose this family when you are moving an existing Word mail-merge document into an automated flow.
How do I configure Mail Merge template in Make?
Set the module fields as below. Required fields are marked with a red asterisk in the Make UI.
| Parameter | Required | What it does | Example |
|---|---|---|---|
| Connection | Required | PDF4me connection for the scenario. Click Add to create one with your API key. | My PDF4me connection |
| Template File Type | Required | Set to PDF4me Word Template for this template family. | PDF4me Word Template |
| Output Type | Required | Format of the generated document. PDF for a locked file or Word for an editable one. | PDF |
| Template Name | Required | Template file name including extension. Map from the prior module file name output. | simple_mail_merge_template.docx |
| Template | Required | Template file binary. Map from the prior module data output (for example 1. Data from Dropbox Download a File). | 1. Data |
| Document DataType | Required | Choose Json for JSON payloads (most common) or Xml when the upstream system returns XML. | Json |
| Document Data Text | Conditional | Inline JSON or XML data. Use when Document Data File is empty. | sample_mail_merge_data.json |
| Document Data File | Conditional | Mapped data file from a prior module. Use when Document Data Text is empty. | 1. Data |
Output
The module returns one bundle per run. The generated file is placed on the Doc Data output field.
| Field | Type | What it contains |
|---|---|---|
Doc Data | Binary | The generated PDF document. Map into a downstream Upload File or Send Email Attachment module. |
File Name | String | Output filename based on Template Name with the extension matching Output Type. |
Mime Type | String | MIME type of the generated document. |
Production patterns
Common Make patterns for mail merge templatesReplace the manual test with these once the sample works.
- Dropbox or Google Drive stores
simple_mail_merge_template.docx. - Download a File loads the template as binary.
- Generate Document Single maps Template Name and Template.
- Data is built from Sheets or a webhook as JSON.
- Webhook receives the record payload.
- Generate Document Single merges it with the template.
- Output Type is PDF.
- Send Email or Upload File delivers Doc Data.
- Search Records returns many rows.
- Iterator loops one record at a time.
- Generate Document Single runs once per record.
- Each file is uploaded to a per-record folder.
Frequently Asked Questions
Related Guides
For the underlying template engine, see the Aspose Words for .NET documentation and the Make data structures reference.