Generate Document Single in Make

What this module does

PDF4me Generate Document Single merges a Word, HTML, or PDF 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.

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 extension

The Template File Type dropdown (PDF4me Word Template, PDF4me HTML Template, PDF4me PDF Template) must match the file mapped under Template. A .docx file mapped with HTML selected as the type fails at run time. Word templates use mustache style placeholders such as {{customer.name}}.

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.

Make PDF4me Generate Document Single module. Connection is set to test prod account. Template File Type is PDF4me Word Template. Output Type is Word. File source is Map with Template Name mapped from previous step File Name and Template mapped from previous step Data. Document DataType is Json and Document Data Text shows an inline JSON object with Name, Age, and Birth fields. Document Data File and Meta Data Json are empty. Cancel and Save buttons at the bottom. — Generate Document Single module configuration in Make. Required fields (red asterisk): Connection, Template File Type, Output Type, Template Name, Template, and Document DataType. With File Selection set to Map, wire Template Name and Template from the prior module; supply data via Document Data Text or Document Data File.

Parameters

Required in the Make UI: Connection, Template File Type, Output Type, Template Name, Template, and Document DataType (all marked with red asterisks in the module). 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	Yes	PDF4me connection for the scenario. Click Add to create a connection with your API key, or select an existing connection from the dropdown.	`test prod account`
Template File Type	Yes	Select template file type. PDF4me Word Template for .docx (mustache variables), PDF4me HTML Template for .html, PDF4me PDF Template for .pdf (form field replacement).	`PDF4me Word Template`
Output Type	Yes	Format of the generated document. Word for editable .docx, PDF for print ready locked layout (most common), Excel for .xlsx, HTML for web embedding.	`Word`
File Selection	Yes	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	Yes	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	Yes	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.
Document DataType	Yes	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 , "Birth": "2000-1-1" }`
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.

Template File Type options

Match the type to the extension of the file mapped under Template.

PDF4me Word Template.docx with mustache placeholders

Most flexible option. Supports template variables like {{customer.name}}, loops, conditionals, tables, and inline images. Best for invoices, contracts, certificates, and letters.

PDF4me HTML Template.html with inline CSS

Use when your team already maintains HTML or email templates. Placeholders are substituted at render time. Good for marketing PDFs and brand styled invoices.

PDF4me PDF TemplateFillable PDF form field replacement

Use when you have a fixed layout fillable PDF (government form, regulatory document). The module fills named form fields with your data and returns the populated PDF.

Output Type options

Pick the format that matches what downstream Make modules expect.

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 added.

ExcelSpreadsheet .xlsx output

Use for data heavy templates such as financial reports or pivot ready tables. 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.

Document DataType options

Pick the data format produced by your upstream system.

JsonMost common in Make

JSON payloads map cleanly from upstream Make modules (HTTP, Webhook, Airtable, Google Sheets). Paste inline JSON into Document Data Text or build it with Make expressions.

XmlFor XML native systems

Use when your source system (ERP, banking, government) returns XML and you do not want to convert it to JSON first. The template engine handles XPath style references.

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, etc).

Scenario examples

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

Dropbox template + webhook data to email PDF

Webhook receives JSON for a new invoice.
Dropbox Download a File loads the invoice Word template.
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.
Email Send Email attaches Doc Data to send the invoice to the customer.

Airtable certificates upload to Google Drive

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

Google Sheets row to monthly report PDF

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

Frequently Asked Questions

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

Three options under Template File Type: PDF4me Word Template (.docx with mustache style template variables, most common), PDF4me HTML Template (.html for browser rendered layouts), and PDF4me PDF Template (.pdf for form field replacement on a fillable PDF). Match the type to the extension of the file mapped under Template.

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 (unlike the n8n version where it is required). 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.

Where does the generated file appear in the bundle?+

The output is on the Doc Data field of the module bundle. Pick Doc Data in the visual mapper of a downstream module such as Upload File, Send Email Attachment, or any module that accepts binary input. The filename uses Template Name with the extension matching Output Type.

How do I generate many documents in one scenario?+

For one document per record processing, 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 (one PDF with one record per page) 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 option, n8n is the developer friendly self hosted option, Zapier triggers from any of 6,000+ SaaS apps, and Power Automate is the Microsoft 365 native option. The template logic and output format are identical across platforms.

Can I generate documents using a PDF form template instead of Word?+

Yes. Set Template File Type to PDF4me PDF Template and map a fillable PDF under Template. The module fills named form fields with your data and returns the populated PDF. Use this path when you have a fixed layout regulatory or government form that cannot be redesigned as a Word template.

Generate Documents Multiple

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

Parse a Document

Companion module for the reverse direction: extract structured data out of a PDF using a saved parse template.

REST API reference

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