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

Drop a Word template (e.g. simple_mail_merge_template.docx) into a Dropbox folder and keep a JSON file (e.g. sample_mail_merge_data.json) in the same place. When a new file appears, Zapier can run a mail merge: find the JSON, call PDF4me – Generate Document (Template File Type: Mail Merge), upload Word, run Generate Document again for PDF, then upload. Six steps. Trigger-based. No manual run.

The screenshots match the folder paths, file names, and PDF4me options you set in Zapier—map trigger → find JSON → PDF4me → upload using the same values shown in each image.

Why-Based Q&A​

---

What You'll Get​

Trigger: A new file in the watched Dropbox folder (e.g. a new or updated template). Input: The triggering file as template and a fixed JSON file (sample_mail_merge_data.json) in the same folder. Output: Word and PDF in /Generate document Mail Merge/Output as Mail_Merge_Zap_deployed.docx and Mail_Merge_Zap_deployed-2.pdf (or your chosen names). Overwrite off so prior runs are kept unless you change names.

---

What You Need​

---

The Zap at a Glance (6 Steps)​

1. Dropbox – New File in Folder — Folder /Generate document Mail Merge. Include file contents: Yes (and sharing link if needed).
2. Dropbox – Find a file — Same folder, file name sample_mail_merge_data.json, include file contents: Yes.
3. PDF4me – Generate Document — Template from step 1. Template File Type: Mail Merge. Input Data Format Type: File. Data File from step 2. Input Data Type: Json.
4. Dropbox – Upload File — /Generate document Mail Merge/Output. File from step 3. Overwrite: No. Name: Mail_Merge_Zap_deployed. Extension: .docx.
5. PDF4me – Generate Document — Same template (step 1). Template File Type: Mail Merge. Input Data Format Type: Text. Data Text — JSON (from step 2 content or a fixed sample). Input Data Type: Json. Output: Pdf where the action exposes it.
6. Dropbox – Upload File — Same Output folder. File from step 5. Overwrite: No. Name: Mail_Merge_Zap_deployed-2. Extension: .pdf.

Complete Zap overview​

Trigger → find JSON → mail merge to Word → upload → second merge to PDF → upload. All steps green when mapping matches the reference.

---

Step 1: New File in Folder (Trigger)​

Zap so far: Trigger only.

1. Dropbox → New File in Folder.
2. Folder — /Generate document Mail Merge.
3. Include file contents? — Yes.
4. Include sharing link? — Yes if your upload steps need it.
5. Test. Step 1 supplies the template file for PDF4me (e.g. simple_mail_merge_template.docx).

New File in Folder: Configuration​

The watched folder is where templates and the JSON file live; a new file starts the Zap.

---

Step 2: Find the JSON data file​

Zap so far: Trigger → Find JSON.

1. Dropbox → Find a file (search by folder + name).
2. Folder — /Generate document Mail Merge.
3. File name — sample_mail_merge_data.json.
4. Include file contents? — Yes.
5. Test. Map this step’s file into PDF4me as Data File for step 3.

Find JSON: Configuration​

Always targets the same JSON path so the merge data is stable even when the trigger file varies.

---

Step 3: PDF4me – Generate Document (template from trigger, data from JSON)​

Zap so far: Trigger → Find JSON → Generate Document.

1. PDF4me → Generate Document.
2. Template File — From step 1 (trigger file).
3. Template File Name / Extension — From step 1 (e.g. simple_mail_merge_template, .docx).
4. Template File Type — Mail Merge.
5. Input Data Format Type — File.
6. Data File — From step 2.
7. Input Data Type — Json.
8. Test. Use the returned file URL or binary in step 4.

Generate Document: Word output​

First pass produces the merged Word document from template + JSON file.

---

Step 4: Upload File (Word)​

Zap so far: Through first Generate Document.

1. Dropbox → Upload File.
2. Folder — /Generate document Mail Merge/Output.
3. File — From step 3.
4. Overwrite — No.
5. File name — Mail_Merge_Zap_deployed. Extension — .docx.
6. Test.

Upload File: DOCX​

Stores the editable mail merge result under a fixed base name.

---

Step 5: PDF4me – Generate Document (second run, PDF)​

Zap so far: Word uploaded; second PDF4me action.

1. PDF4me → Generate Document.
2. Template File — From step 1 (same as first merge).
3. Template File Type — Mail Merge.
4. Input Data Format Type — Text.
5. Data Text — JSON array or object matching your merge fields (e.g. [{"firstname":"John","lastname":"Adams","gender":"Female","member":"Basic"}]), mapped from step 2 if Zapier exposes file content as text.
6. Input Data Type — Json.
7. Set Output Document Type to Pdf when available.
8. Test. Feed step 6 with this step’s file output.

Generate Document: Data Text for PDF​

Second pass uses the same logical data as the JSON file, formatted as text, to emit a PDF.

---

Step 6: Upload File (PDF)​

Zap so far: Full Zap.

1. Dropbox → Upload File.
2. Folder — /Generate document Mail Merge/Output.
3. File — From step 5.
4. Overwrite — No.
5. File name — Mail_Merge_Zap_deployed-2. Extension — .pdf.
6. Turn the Zap on.

Upload File: PDF​

Completes the pair: Word + PDF in Output for each trigger.

---

Real-World Use Cases​

---

Quick Reference​

Step	Key setting	Example
New File in Folder	Folder, file contents	/Generate document Mail Merge
Find file	Folder, file name	sample_mail_merge_data.json
Generate Document	Mail Merge, File data	Template step 1; Data step 2
Upload File	Output, name	Mail_Merge_Zap_deployed.docx
Generate Document	Mail Merge, Text data	JSON; output PDF
Upload File	Output, name	Mail_Merge_Zap_deployed-2.pdf

See Generate Document Single — Zapier. For a manual four-step mail merge on Make, see Mail Merge in Make (four steps).

---

Troubleshooting​

---

What's Next​

1. Test end-to-end — Drop a file into the watched folder and verify both outputs in Output.
2. Polling — Dropbox triggers on Zapier use polling; upgrade or add a Delay if you need spacing between rapid uploads.
3. Single format — Remove the second Generate Document + upload if you only need Word or only PDF.
4. Manual flow — Mail Merge in Make (four steps) without a folder trigger.