Word template in Make
PDF4me Word Template is the most flexible template family in Make Generate Document Single. It takes a standard .docx file with template placeholders that match your JSON or XML keys, and outputs a personalized PDF or Word document. Use it for invoices, contracts, certificates, and letters without any manual mail merge.
Before You Start
template.docx contains placeholders that map to keys in your data file. Placeholder names must match your JSON or XML field names exactly, including nesting.data.json (recommended), test.xml, or test.csv. The same values populate the template regardless of format.Sample File Pack
Download the files below. One Word template plus matching data in JSON, XML, and CSV.
Target configuration: PDF4me Word Template + JSON in Document Data Text + PDF output.
What is the PDF4me Word Template template in Make?
The PDF4me Word Template family merges a Microsoft Word .docx file with your data at run time. The .docx acts as a fully designed layout (logos, tables, styles) and the module replaces the placeholders with values from the data file. It is the recommended choice when your document needs precise formatting and reusable branding.
How do I configure PDF4me Word 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. Word for editable output, PDF for a locked layout (most common). | PDF |
| Template Name | Required | Template file name including extension. Map from the prior module file name output. | 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. | 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 Word templatesReplace the manual test with these once the sample works.
- Dropbox or Google Drive stores
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.