Merge Documents - Document Assembly for Zapier

PDF4me Merge Documents is a Zapier action that combines multiple Word files into a single document. Use Sort Position to control merge order, Format Mode to choose how styles combine, and Compliance Level for document standards conformance. Returns one merged Word file for the next Zap step, no manual copy-paste in Word.

What this action does

Takes two or more Word documents from previous Zap steps and combines them into one file, in the order you set with Sort Position. Choose how each document's formatting carries over with Format Mode, and optionally set a compliance level and time zone for the merged output. Useful for assembling multi-department reports, compiling proposal sections, or combining contract clauses without opening Word.

Related Blog Posts

No blog post yet for this feature — coming soon.

In the meantime, browse the PDF4me blog for tutorials and workflows across every platform.

Visit the blog →

Authenticating Your API Request

To access the PDF4me Web API through Zapier, every request must include proper authentication credentials. Authentication ensures secure communication and validates your identity as an authorized user, enabling seamless integration between your Zapier workflows and PDF4me's Word document merging services.

Get your API Key

Important Facts You Should Not Miss

Only File and File Name are required per document

Sort Position and Format Mode are optional for each document. Compliance Level and Time Zone are optional overall settings.

Set Number of files first

This reveals the matching set of File, File Name, Sort Position, and Format Mode fields for each document, File1/File2 for two documents, File3 onward for more.

Lower Sort Position merges earlier

A cover page or introduction would typically get Sort Position 1 (or 0), with later sections given higher values.

Map File1, File2, etc. from previous steps

Use the + button to map File1, File2 (and File Name1, File Name2) from earlier Zap steps. Set Number of files first to reveal the file fields. Each Word file must provide full content, not "Exists but not shown" references.

File: (Exists but not shown)

If you see "File: (Exists but not shown)" and get errors, select the option that provides the full file content. See Zapier & Power Automate Tips for details.

Configure Merge Documents: set Number of files, then map File1/File Name1 (required) and optionally Sort Position1/Format Mode1.

File2/File Name2 (required), then the optional Compliance Level and Time Zone settings that apply to the whole merge.

What Are the Key Features of Merge Documents?

• Multiple Document Support: Merge any number of Word documents into one
• Flexible Ordering: Control merge order with per-document Sort Position values
• Formatting Options: Choose how styles carry over with 3 Format Mode options
• Compliance Settings: Apply ECMA, Transitional, or Strict compliance levels
• Timezone Metadata: Optionally add timezone information for document tracking

Parameters

Complete list of parameters for the Merge Documents action. Parameter names and order match the Zapier configuration UI shown in the screenshots above.

Quick setup checklist

1. Set Number of files (2, 3, etc.) to reveal the file fields
2. Map File1, File Name1, File2, File Name2 (and beyond) from previous steps
3. Optionally set Sort Position per document for merge order, lower merges earlier
4. Optionally set Format Mode per document and overall Compliance Level/Time Zone

Parameter	Required	What it does	Example
Number of files	Required	How many documents to merge. Determines how many File/File Name/Sort Position/Format Mode field sets appear.	2
File1	Required	First document. Map from a previous step. Must provide full file content.	[2. File from Step 2]
File Name1	Required	Filename for the first document, with .docx or .doc extension.	abc.docx
Sort Position1	Conditional	Merge order for the first document. Lower values merge earlier.	1
Format Mode1	Conditional	Formatting for the first document: KeepSourceFormatting, KeepDifferentStyles, or UseDestinationStyles.	KeepSourceFormatting
File2	Required	Second document. Map from a previous step.	[4. File from Step 4]
File Name2	Required	Filename for the second document.	abcd.docx
Sort Position2, Format Mode2	Conditional	Same pattern as document 1. Repeats for File3, File4, and so on if Number of files is greater than 2.	2
Compliance Level	Conditional	Document standard for the merged output: ECMA, Transitional, or Strict.	Custom
Time Zone	Conditional	Timezone applied to document metadata in the merged file.	UTC

Important: Number of files, and File/File Name for each document, are required. Sort Position, Format Mode, Compliance Level, and Time Zone are all optional.

What Does Merge Documents Return?

The PDF4me Merge Documents action returns the merged Word file for use in subsequent Zap steps. The output format is common across all PDF4me Word file-returning actions in Zapier.

Key output fields (map these to your next step)

File Url

API endpoint to download the merged Word file. Map this to the next step's file input.

api.pdf4me.com/Zapier/GetDocument?d=...

Alternate File Url

Alternative download URL with filename in path.

api.pdf4me.com/Zapier/GetAltDocument/.../merged.docx

Field	Type	What it contains
Job Id	String	Unique identifier for the Zapier job execution.
File Url	URL	API endpoint to download the merged Word file.
Alternate File Url	URL	Alternate download URL with the filename in the path.
File Name	String	Base filename without extension.
Full File Name	String	Complete filename with extension.
File Extension	String	File extension of the returned file, .docx.

JSON

Example JSON output (URLs show format only, not working links):

{
"Job Id": "...",
"File Url": "api.pdf4me.com/Zapier/GetDocument?d=...",
"Alternate File Url": "api.pdf4me.com/Zapier/GetAltDocument/.../merged.docx",
"File Name": "merged",
"Full File Name": "merged.docx",
"File Extension": ".docx"
}

Zap Integration

Use + to map File Url or Alternate File Url to the next step, Drive, Dropbox, Email, or another PDF4me Word action.

Typical Setups

Workflow ExamplesCommon Zapier workflow patterns using Merge Documents.

Multi-department report assembly

1. A trigger fires once all department report sections have been submitted.
2. PDF4me Merge Documents combines the cover page, executive summary, and each department section, using Sort Position to control the final order and Format Mode set to KeepSourceFormatting to preserve each section's own styling.
3. The consolidated report uploads to an executive reports folder.

RFP proposal compilation

1. A trigger fires when all proposal sections are marked approved.
2. PDF4me Merge Documents combines the cover letter, technical approach, pricing, and team bios with Format Mode set to UseDestinationStyles for a consistent look across sections written by different teams.
3. The finished proposal uploads to the submissions folder for sales leadership to review.

Contract assembly from a clause library

1. A trigger fires once negotiated contract terms are finalized.
2. PDF4me Merge Documents combines standard clauses, custom terms, schedules, and the signature page, with Format Mode set to KeepDifferentStyles to preserve each clause's original formatting variations.
3. The assembled contract routes to the legal team for final review.

Practical Tips

File: (Exists but not shown) causes errors

Select the mapping option that provides each file's full binary content instead of a reference.

Set Number of files before mapping documents

The File, File Name, Sort Position, and Format Mode fields for each document only appear after Number of files is set.

Sort Position ties are possible

If two documents share the same Sort Position, the merge order between them is not guaranteed, use distinct values for predictable ordering.

UseDestinationStyles is safest for mixed sources

When documents come from different authors or templates, UseDestinationStyles avoids clashing fonts and heading styles better than KeepSourceFormatting.

Compliance Level and Time Zone apply to the whole merge

Unlike Sort Position and Format Mode, these two settings are not per-document, they affect the merged output as a whole.

Cheat Sheet

Field	Value
Action	Merge Documents
Number of files	2
File1 / File Name1	[Mapped] / abc.docx
Sort Position1	1
File2 / File Name2	[Mapped] / abcd.docx
Sort Position2	2
Format Mode	KeepSourceFormatting (optional)
Compliance Level	Transitional (optional)

Common Questions

How do I merge multiple Word documents automatically in Zapier?+

Add the PDF4me Merge Documents action to a Zap, set Number of files, map each File and File Name from previous steps, and set a Sort Position for each. See Adobe's guide on combining Word documents for the manual alternative this action automates.

How do I control the order documents are merged in?+

Set Sort Position1, Sort Position2, and so on for each document. Lower Sort Position values are placed earlier in the merged output, so a cover page would typically get the lowest value.

What is the difference between the Format Mode options?+

KeepSourceFormatting preserves each document's own styles as-is. KeepDifferentStyles keeps distinct styles but avoids naming conflicts between documents. UseDestinationStyles reformats each document to match the base document's styles for a consistent look.

Is Sort Position required for every document?+

No. Only Number of files, and File and File Name for each document, are required. Sort Position and Format Mode are optional per document, along with the overall Compliance Level and Time Zone settings.

Can I merge more than two Word documents at once?+

Yes. Set Number of files to the total count, which reveals a File, File Name, Sort Position, and Format Mode field set for each document. See Zapier's guidance on setting up actions for general help configuring repeating fields in a Zap.

Related Actions

Optimize Document

Reduce the merged file's size after assembly, useful for large multi-section documents before email distribution.

Update Headers Footers

Add consistent page numbers or a company header/footer across the newly merged document.

Secure Document

Password-protect or restrict editing on the final assembled document before distribution.

Same Task on Other Platforms

Merge Documents in Make

Same document-assembly module, wired into visual Make scenarios with cloud-storage triggers.

Merge Word Documents in n8n

The equivalent n8n node for developers who want the merge logic inside a self-hosted or code-heavy workflow.

Merge Documents in Power Automate

Microsoft 365 flows with SharePoint and OneDrive for organizations already standardized on Power Automate.

Merge Documents REST API

The raw PDF4me API endpoint behind this action, for custom backend code or Postman testing.

Industry Use Cases & Applications

Legal & Professional

• Contract Assembly: Merge standard clauses with custom terms into complete contracts
• Legal Brief Compilation: Combine argument sections, exhibits, authorities into final briefs
• Discovery Document Assembly: Merge privilege logs with responsive documents for production
• Matter File Consolidation: Combine case memos, pleadings, correspondence into matter summaries
• Opinion Letter Assembly: Merge research memos with opinion boilerplate into client letters

Corporate & Business

• Proposal Compilation: Merge cover letter, technical approach, pricing, bios into RFP responses
• Report Assembly: Combine executive summary with department sections into consolidated reports
• Business Plan Consolidation: Merge plan sections (market, operations, financials) into complete plans
• Board Package Assembly: Combine agenda, reports, resolutions into board meeting packages
• Strategic Plan Compilation: Merge vision, goals, initiatives into comprehensive strategic plans

Human Resources

• Employee Handbook Assembly: Merge policy sections into complete employee handbooks
• Onboarding Package Creation: Combine welcome letter, forms, policies into new hire packets
• Benefits Guide Compilation: Merge benefit plan descriptions into comprehensive benefits guides
• Performance Review Assembly: Combine evaluation forms with development plans into review documents
• Training Manual Consolidation: Merge training modules into complete training manuals

Publishing & Documentation

• Book Manuscript Assembly: Merge chapter documents into complete manuscript for publishing
• Technical Manual Compilation: Combine technical sections into comprehensive user manuals
• Course Material Assembly: Merge lesson modules into complete course materials
• Documentation Consolidation: Combine API docs, guides, tutorials into unified documentation
• Report Publishing: Merge report components into publication-ready documents

Get Help

Zapier IntegrationGet your API KeyZapier Documentation