Google Docs Template + JSON? Make Turns Them Into PDFs or Word. Four Steps, Zero Code!
You have a Google Docs template with placeholders (e.g. {{name}}, {{course}}, {{date}}) and data in JSON. Manually copying values into each document is slow and scales poorly. With Make and PDF4me, you can automate it: download the template and JSON from Dropbox, run PDF4me – Generate Document with Template File Type: Google Docs and Output Type: Pdf (or Word), then upload the generated file. Four modules. One scenario. No code.
This guide follows current market standards: In a nutshell, What You Need, step-by-step with screenshots and descriptive alt text, real-world use cases, Quick Reference, Troubleshooting, and links to the action docs.
In a nutshell: Dropbox – Download a File (template, e.g. /Generate document Mail Merge/Google Docs Template.docx) → Dropbox – Download a File (JSON data, e.g. /Generate document Mail Merge/Google Docs data.json) → PDF4me – Generate Document (Template File Type: Google Docs, Output Type: Pdf or Word, map Template and Document Data from steps 1 and 2) → Dropbox – Upload a File to your output folder. Result: one generated PDF or Word document per run.
What You'll Get
Input: A Google Docs–compatible template (e.g. exported as .docx or stored in a format the connector accepts) and a JSON file whose keys match the template placeholders. Output: A single PDF or Word document with placeholders replaced by the JSON values—saved to your Dropbox output folder (e.g. Google_Make_Prod.pdf or Google_Make_Prod_2.docx).
What You Need
- Make — Create a Make account and open a new scenario.
- PDF4me API key — Get your API key. Connect it when you add the PDF4me module. First time? See Connect PDF4me to Make.
- Dropbox — For template file, JSON file, and output folder. The connector needs Download a File and Upload a File. Google Drive or other storage with similar actions works too.
- Google Docs template — A document with merge fields (e.g. mustache
{{name}}or merge-field names). Export or save it so it can be stored in Dropbox (e.g. as .docx). Template File Type in PDF4me is set to Google Docs. - JSON data — One object with keys matching the template placeholders (e.g.
name,course,date,instructor). Stored as a file in Dropbox or provided from a previous module.
The Scenario at a Glance (4 Modules)
- Dropbox – Download a File (1) — Fetches the template file (e.g.
Google Docs Template.docx). - Dropbox – Download a File (2) — Fetches the JSON data file (e.g.
Google Docs data.json). - PDF4me – Generate Document (5) — Template File Type: Google Docs, Output Type: Pdf or Word. Template content and name from step 1; document data from step 2 (Document Data File or Document Data Text). Document DataType: Json.
- Dropbox – Upload a File (6) — Saves the generated document to the output folder. File content from PDF4me Document; set File Name and Overwrite an existing file (Yes/No) as needed.
Complete scenario overview

Fact-checked: Dropbox 1 and 2 download template and JSON; PDF4me 5 generates the document (Template File Type Google Docs); Dropbox 6 uploads to /Generate document Mail Merge/Output/. Step numbers (5, 6) reflect typical scenario order.
Step 1: Download the Template from Dropbox
Scenario so far: First Download only.
- Add Dropbox → Download a File.
- Connection — Select your Dropbox connection (e.g. YnooxTestone).
- Way of selecting files — Select a file (or use Map for dynamic paths from a trigger).
- File — Enter the path to your template, e.g.
/Generate document Mail Merge/Google Docs Template.docx. - Save. The module output (e.g. Data or File) will be mapped into PDF4me as Template and Template Name (e.g. 1. File Name).
Dropbox – Download a File: Template

Fact-checked: Connection required; Way of selecting files = Select a file; File shows /Generate document Mail Merge and Google Docs Template.docx. Output (1. File Name, 1. Data) maps to PDF4me Template Name and Template.
Step 2: Download the JSON Data
Scenario so far: Download template → Download JSON.
- Add a second Dropbox → Download a File.
- Connection — Same Dropbox connection.
- Way of selecting files — Select a file (or Map).
- File — Path to your JSON file, e.g.
/Generate document Mail Merge/Google Docs data.json. - Save. The output Data (file content) will be passed to PDF4me as Document Data File (or use Document Data Text if you prefer to pass a string from another source).
Dropbox – Download a File: JSON data

Fact-checked: Same Connection and Way of selecting files; File path set to Google Docs data.json. Map this module’s Data output to PDF4me Document Data File (2. Data).
Step 3: PDF4me – Generate Document (Google Docs + JSON)
Scenario so far: Download template → Download JSON → Generate Document.
- Add PDF4me → Generate Document.
- Connection — Select your PDF4me connection (e.g. TestUser01).
- Template File Type * — Select Google Docs from the dropdown. (Other options in the UI: PDF4me Word Template, Html, Mail Merge, Pdf Form.)
- Output Type * — Select Pdf for a PDF output or Word for a .docx output.
- File (template source) — Choose Map, then map:
- Template Name * — From the first Dropbox Download (e.g. 1. File Name).
- Template * — From the first Dropbox Download (e.g. 1. Data).
- Document Data File — Map the second Dropbox Download output (e.g. 2. Data). Alternatively, use Document Data Text and paste or map a JSON string.
- Document DataType * — Json.
- Document Data Text — Leave empty if using Document Data File; otherwise paste or map your JSON (e.g.
{"name":"Alice Johnson","course":"Intro to Automation","date":"2026-03-10","instructor":"Mr. Smith"}). - Meta Data Json — Optional. Use for field formatting (dates, checkboxes, etc.) if needed.
- Save. The module returns Document (and Name) — use Document in the Upload step.
Template File Type: Google Docs

Fact-checked: Template File Type * required; dropdown shows Google Docs selected. Other options visible in UI: PDF4me Word Template, Html, Mail Merge, Pdf Form. Use Google Docs for templates with merge placeholders.
Output Type: Pdf or Word

Fact-checked: Output Type * required; choose Pdf for PDF or Word for .docx. Map toggle available for dynamic output format.
Generate Document: Full configuration

Fact-checked: Connection (e.g. TestUser01); File = Map with Template Name 1. File Name and Template 1. Data from Download 1; Document Data File 2. Data from Download 2, or Document Data Text with JSON (e.g. name, course, date, instructor). Document DataType Json. Output Document used in Upload.
Step 4: Upload the Generated Document to Dropbox
Scenario so far: Download template → Download JSON → Generate Document → Upload.
- Add Dropbox → Upload a File.
- Connection — Same Dropbox connection.
- Folder — Output path, e.g.
/Generate document Mail Merge/Output/. - File — Map the Document output from PDF4me – Generate Document (e.g. 5. Document or 7. Document, depending on module order).
- File Name — e.g.
Google_Make_Prod.pdforGoogle_Make_Prod_2.docx. Use the same extension as your Output Type (Pdf → .pdf, Word → .docx). - Overwrite an existing file — Yes to replace an existing file with the same name; No to have Make rename the new file if one already exists.
- Save and run the scenario. The generated PDF or Word file appears in the output folder.
Dropbox – Upload a File

Fact-checked: Folder * = /Generate document Mail Merge/Output/; File source = Map from PDF4me Generate Document (e.g. 5. Document or 7. Document); File Name * = Google_Make_Prod.pdf or Google_Make_Prod_2.docx; Overwrite an existing file = Yes to replace, No to rename. Advanced settings available.
Real-World Use Cases
Certificates and training: Course completion or event data in JSON (name, course, date, instructor). Generate personalized certificates from a Google Docs template and save as PDF for distribution or archival.
Reports and proposals: Pull data from Airtable, Google Sheets, or a database; output JSON. Merge into a Google Docs report template and generate PDF or Word for clients or internal use.
Invoices and quotes: Order or quote data as JSON. Template with placeholders for customer, amount, date; generate PDF or Word and upload to a shared folder or attach to an email in a follow-up module.
Mail merge at scale: Use a single scenario run per document, or combine with Make iterators to generate many documents from a list of JSON objects—each with its own output file name.
Quick Reference
| Module | Key setting | Example / output |
|---|---|---|
| Dropbox Download (1) | File | /Generate document Mail Merge/Google Docs Template.docx → Template + Template Name |
| Dropbox Download (2) | File | /Generate document Mail Merge/Google Docs data.json → Document Data File (2. Data) |
| PDF4me Generate Document | Template File Type | Google Docs |
| PDF4me Generate Document | Output Type | Pdf or Word |
| PDF4me Generate Document | Template Name / Template | 1. File Name, 1. Data |
| PDF4me Generate Document | Document Data File / Document DataType | 2. Data, Json |
| PDF4me Generate Document | Output | Document (and Name) |
| Dropbox Upload | Folder, File, File Name | Output path, 5. Document (or 7. Document), Google_Make_Prod.pdf |
For full parameter details, see Generate Document Single — Make. The PDF4me connector in Make also supports Template File Type: Google Docs for templates designed for Google Docs–style merge.
Troubleshooting
JSON keys must match the template placeholders (e.g. name, course, date). Check the template for exact placeholder names and use the same keys in your JSON. Document DataType must be Json when passing JSON.
Map the actual Data (or file content) from each Dropbox Download—not the file path. Template = first Download’s content; Document Data File = second Download’s content. Use the correct step numbers (e.g. 1. Data, 2. Data) in the mapping panel.
Check PDF4me Troubleshooting for 401 (API key), 402 (credits), and connection issues.
What's Next
- Run the scenario — Add a template and JSON file to the configured Dropbox paths and run once. Confirm the generated PDF or Word file in the output folder and that all placeholders are filled.
- Automate — Replace manual trigger with When a file is created (Dropbox) or a webhook; use Map to pass the new file path to the Download modules for template or data.
- Batch — Use an iterator over a list of JSON objects (or multiple JSON files); run Generate Document and Upload inside the loop to produce one output file per item.
- Try the API — Use the API Tester or the Generate Document Single docs to test template types and output formats.