Generate Document Single in Make

Generate Document Single is a PDF4me module for Make that merges one template with one set of data and returns a single finished document per run. It supports five template families (Word, HTML, PDF form, Mail Merge, and Google Docs) and two data formats (JSON and XML), and outputs PDF, Word, Excel, or HTML. Use it for invoices, contracts, certificates, and personalized letters without writing code.

What this module does

PDF4me Generate Document Single merges a Word, HTML, PDF, Mail Merge, or Google Docs template with JSON or XML data and produces a personalized PDF, Word, Excel, or HTML file in one Make module. It replaces multi-step mail-merge scenarios with a single configurable action. Map the template file from any cloud storage module (Dropbox, Google Drive, OneDrive), supply your data inline or as a mapped file, and pipe the generated Doc Data output straight into Upload File, Send Email, or any downstream Make module.

Related Blog Posts(4)

Google Docs Template + JSON? Make Turns Them Into PDFs or Word. Four Steps, Zero Code!

Generate PDF or Word from a Google Docs template in Make: Dropbox (template + JSON) → PDF4me Generate Document (Template File Type Google Docs) → Upload. Merge placeholders with data, no code. Step-by-step with screenshots.

Read post →

Word Template + JSON in Dropbox? Run a Mail Merge in Make. PDF or Word in Four Clicks!

Automate mail merge in Make: Dropbox (Word template + JSON) → PDF4me Generate Document (Template File Type Mail Merge) → Upload. Merge placeholders with data, output PDF or Word. Step-by-step with screenshots.

Read post →

New File in Your Dropbox Folder? Run a Mail Merge in Make. Six Steps, Fully Automated!

Trigger-based mail merge in Make: when a new file appears in Dropbox, find the JSON data, run PDF4me Generate Document (Mail Merge), then upload Word and PDF. Step-by-step with screenshots.

Read post →

Choose your template type

Pick the guide that matches your Template File Type. Each page lists the exact sample template, data files (JSON, XML, CSV), recommended field values, and a quick test scenario for Make.

PDF4me Word Template

Standard .docx with mustache placeholders. Output PDF or Word. Includes template.docx + data.json.

HTML

HTML file or pasted HTML Code. Render a branded invoice. Includes invoice HTML + JSON data.

Pdf Form

AcroForm PDF template. Output PDF. Includes template.pdf + formdata.json.

Mail Merge

Word mail-merge fields. Output PDF or Word. Includes simple_mail_merge_template.docx.

Google Docs

Google Docs export style .docx. Output PDF or Word. Includes google-docs-template.docx.

Authenticating Your API Request

Every PDF4me module in Make requires a valid Connection. Create or select one that holds your PDF4me API key so the scenario can authenticate document generation requests securely.

Get your API Key

Important Facts You Should Not Miss

Template File Type must match the template file

The Template File Type you pick must match the file mapped under Template. A .docx mapped with an HTML type selected fails at run time. Open the matching guide above for the exact placeholder syntax each template family uses.

Provide either Document Data Text or Document Data File

Document Data Text accepts inline JSON or XML and is best for short payloads mapped from earlier modules. Document Data File accepts a binary file from a previous Make step and is best for large or pre-built data documents. Use one or the other in each scenario.

The output is on Doc Data, ready for the next module

The generated file is returned on the Doc Data output field. Pipe it directly into Upload File (Dropbox, Drive, OneDrive), Send Email Attachment, or any downstream module that accepts binary. The filename is preserved from the Template Name field.

Pick a Template Name from your PDF4me repository, set Document Data Type to Json, and map Document Data File from a prior download step (or paste JSON into Document Data Text instead).

What parameters does Generate Document Single use in Make?

Required in the Make UI: Connection, Template File Type, Output Type, Template Name, Template, and Document DataType (all marked with red asterisks). Conditional: Document Data Text OR Document Data File (one of the two must carry the data payload). Optional: Meta Data Json.

Parameter	Required	What it does	Example
Connection	Required	PDF4me connection for the scenario. Click Add to create a connection with your API key, or select an existing connection from the dropdown.	My PDF4me connection
Template File Type	Required	Select the template family: Word Template (.docx), HTML (.html), Pdf Form (fillable .pdf), Mail Merge (.docx merge fields), or Google Docs export (.docx). Open the matching guide for placeholder syntax.	PDF4me Word Template
Output Type	Required	Format of the generated document. Word for editable .docx, PDF for print-ready locked layout (most common), Excel for .xlsx, HTML for web embedding.	PDF
File Selection	Required	How the template file is supplied. Choose a storage module shortcut (for example Dropbox Download a File) or select Map to wire Template Name and Template from any prior step.	Map
Template Name	Required	Template file name including extension. Map from the previous module filename output (shown as 1. File Name when Dropbox Download a File is upstream).	1. File Name
Template	Required	Template file binary for document generation. Map from the previous module data output (shown as 1. Data when Dropbox Download a File is upstream).	1. Data
Document Data File	Conditional	Map source document file content from a previous action when your data payload is a file rather than inline text. Use when Document Data Text is empty.	1. Data
Document DataType	Required	Choose document data type. Json for JSON payloads (most common), Xml when the upstream system returns XML.	Json
Document Data Text	Conditional	Input data text to generate the document. Paste JSON or XML inline or build it with Make expressions. Use when Document Data File is empty.	{ "Name": "John", "Age": 16 }
Meta Data Json	No	Optional metadata for template fields (title, author, subject, custom properties). Shown without an asterisk in the Make UI. Leave empty for most templates.

How do I choose the Output Type in Make?

Pick the format that matches what downstream Make modules expect. The output format is independent of the template type, so a Word template can produce a PDF.

PDFPrint-ready, locked layout

Standard choice for invoices, contracts, certificates, and statements. Send via Email or upload to storage as a final deliverable.

WordEditable .docx output

Use when the recipient needs to edit the generated document such as draft contracts that go back for review or HR letters that need a manual signature line.

ExcelSpreadsheet .xlsx output

Use for data-heavy templates such as financial reports. The template must be designed in Excel and use Excel template variable syntax.

HTMLWeb-ready HTML

Use for emails, web previews, or downstream rendering in a browser-based viewer. Output is a single HTML file.

Output

The module returns one Bundle per execution. The generated file is placed on the Doc Data output field, ready for downstream modules to pick up via the standard Make data mapping.

Field	Type	What it contains
Doc Data	Binary	The generated document in the format chosen under Output Type. Map this into a downstream Upload File, Send Email Attachment, or any module that accepts binary input.
File Name	String	Output filename based on Template Name with the extension matching Output Type.
Mime Type	String	MIME type of the generated document (application/pdf, application/vnd.openxmlformats-officedocument.wordprocessingml.document, and so on).

Scenario examples

Common Make scenario patternsTypical ways to chain Generate Document Single into a Make flow.

Dropbox template + webhook data to email PDF

1. Webhook receives JSON for a new invoice.
2. Dropbox Download a File loads the invoice Word template.
3. Generate Document Single maps Template Name and Template from the Dropbox step, sets DataType to Json, and reads the webhook JSON into Document Data Text.
4. Email Send Email attaches Doc Data to send the invoice to the customer.

Airtable certificates upload to Google Drive

1. Scheduled trigger fires daily at 09:00.
2. Airtable Search Records fetches new course completions.
3. Iterator loops over each record.
4. Generate Document Single merges the Word certificate template with the record data and outputs PDF.
5. Google Drive Upload a File saves each certificate to a shared folder named after the recipient.

Google Sheets row to monthly report PDF

1. Schedule fires on the first of every month.
2. Google Sheets Search Rows pulls the monthly aggregation data.
3. Transform module shapes the rows into the JSON structure the template expects.
4. Generate Document Single renders the report template with the data, Output Type PDF.
5. OneDrive Upload a File archives the PDF and Slack Send a Message posts a download link.

Frequently Asked Questions

Which template file types does Generate Document Single accept in Make?+

Five template families: PDF4me Word Template (.docx with mustache variables, most common), HTML (file or pasted HTML Code), Pdf Form (fillable .pdf form-field replacement), Mail Merge (Word mail-merge fields), and Google Docs (Google Docs export style .docx). Each has its own setup guide with sample files linked in the Choose your template type section above.

What output formats can the Make module produce?+

Output Type supports Word (.docx for editable output), PDF (locked layout, most common for invoices and contracts), Excel (.xlsx for spreadsheet output), and HTML for web embedding. The output format is independent of the template type, so a Word template can produce a PDF and vice versa.

How do I pass JSON data to the template?+

Set Document DataType to Json, then either paste the JSON object directly into Document Data Text or map a data file from a previous module into Document Data File. Document Data Text is best for small payloads built with Make expressions, Document Data File is best for large or pre-built data documents.

Is Meta Data Json required?+

Meta Data Json is shown without an asterisk in the Make UI, so it is optional in this connector. Use it when your template references document metadata such as title, author, or subject at render time. Leave it empty for most invoice and contract scenarios.

How do I generate many documents in one scenario?+

For one document per record, add a Make Iterator or Search Records loop before Generate Document Single and map each record into the data field. The module runs once per record and returns one file per execution. For true multi-record output in a single call use Generate Documents Multiple instead.

How is this different from the n8n, Zapier, or Power Automate version?+

All four platforms call the same PDF4me Generate Document Single backend. Make is the visual scenario builder, n8n is the developer-friendly self-hosted option, Zapier triggers from 6,000+ SaaS apps, and Power Automate is Microsoft 365 native. The template logic and output format are identical across platforms.

Related actions

Generate Documents Multiple

Generate one document with many records in a single call. Use for batch reports and bulk personalized mailings.

Generate Document Single in n8n

The same engine as a self-hosted n8n node with sample files for every template type.

REST API reference

Same engine via the raw PDF4me REST API. Use when you want to call from custom code outside Make.

Get Help

For the template engine and mustache syntax that powers every template family, see the Aspose Words for .NET documentation and the Make data structures reference.

Get Your API KeyPDF4me on MakeMake Integration Guide