Skip to main content
PDF4me APIIntegrationsGeneral GuidelinesExtensionsAPI Tester

Merge Documents - Document Assembly for Zapier

PDF4me Merge Documents action enables combining multiple Word documents into a single document within Zapier workflows with advanced formatting and compliance options. This powerful document merging service supports flexible document ordering with SortPosition, customizable formatting modes (KeepSourceFormatting, KeepDifferentStyles, UseDestinationStyles) per document, compliance level settings (ECMA, Transitional, Strict), timezone metadata for document tracking, and intelligent style handling with full control over merge behavior—perfect for document assembly, report consolidation, content management, contract compilation, and multi-document packaging workflows across cloud storage platforms and business applications.

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 powerful Word document merging services.

Get your API Key
Merge Documents Zapier

Key Features​

  • Multiple Document Support: Merge unlimited number of Word documents into one
  • Flexible Ordering: Control merge order with customizable SortPosition values
  • Formatting Options: Choose how to handle styles during merge (3 modes)
  • Compliance Settings: Apply different compliance levels (ECMA, Transitional, Strict)
  • Timezone Metadata: Add timezone information for document tracking
  • Style Management: Intelligent handling of document styles and formatting
  • Base Document Concept: First document (lowest SortPosition) becomes foundation
  • Metadata Preservation: Maintain document properties and custom metadata

Parameters​

Complete list of parameters for the Merge action. Configure these parameters to control document merging behavior.

Important: Parameters marked with an asterisk (***) are required. The Documents array must contain at least one document with all required properties.

ParameterTypeDescriptionExample
Documents***ArrayArray of Documents to Merge
• Array of document objects to merge
• Must contain at least one document
• Documents merged in ascending SortPosition order
• Each object requires: Filename*, DocContent*, SortPosition*
• Optional per document: FormatMode
• Lowest SortPosition becomes base document
• Document with lowest SortPosition = base, others appended		[{"Filename":"doc1.docx","DocContent":"[Base64]","SortPosition":0}]
Documents[].Filename***StringDocument Filename
• Original filename of document
• Must include file extension (.docx, .doc)
• Used for reference and processing
• Supports dynamic naming		document1.docx
Documents[].DocContent***FileDocument Content
• Base64-encoded binary content
• Map from previous step
• Must be valid Word format (.docx, .doc)		[File]
Documents[].SortPosition***NumberMerge Order Position
• Position in merge order (ascending)
• Lowest SortPosition becomes base document
• Must be unique within array
• Can use any numbering (0,1,2 or 10,20,30)		0
Documents[].FormatModeStringFormatting Mode
• "KeepSourceFormatting" - Preserves original formatting (default)
• "KeepDifferentStyles" - Keeps different styles, merges similar
• "UseDestinationStyles" - Uses base document formatting
• Controls style handling during merge		KeepSourceFormatting
Merge Options Time ZoneStringDocument Timezone Metadata
• Timezone for document metadata
• Examples: "UTC", "America/New_York", "Europe/London"
• Added as custom document property
• Used for tracking and compliance
• Default: null		UTC
Merge Options Compliance LevelStringDocument Compliance Level
• "ECMA" - ECMA-376 2006 standard
• "Transitional" - ISO 29500:2008 Transitional (default)
• "Strict" - ISO 29500:2008 Strict
• "Custom" - Custom compliance
• Affects document OOXML compliance		Transitional

Output​

The PDF4me Merge Documents action returns comprehensive output data for seamless Zapier workflow integration:

Table View

ParameterTypeDescription
FileURLDirect URL to access the merged Word document
File NameStringThe filename without extension
Full File NameStringComplete filename with .docx extension
File ExtensionStringFile extension (.docx)

Scenario Examples​

The PDF4me Merge Documents action in Zapier provides comprehensive scenario templates:

Automated Multi-Department Report Assembly Workflow

Complete Scenario Steps:

  1. Trigger: Monthly department reports all submitted
  2. Get Cover Page: Retrieve from templates (SortPosition = 0)
  3. Get Executive Summary: From summary folder (SortPosition = 1)
  4. Get Department Sections: Loop through 5 departments (SortPosition = 2-6)
  5. Build Documents Array: Add all with FormatMode = "KeepSourceFormatting"
  6. Set Compliance: Merge Options Compliance Level = "Transitional"
  7. Set Timezone: Merge Options Time Zone = "UTC"
  8. Merge All Sections: Combine into single consolidated report
  9. Upload Final Report: Save to executive reports folder
  10. Email Leadership: Send consolidated report to C-suite

Business Benefits:

  • Assembles 12 monthly executive reports automatically
  • SortPosition ensures correct section ordering
  • KeepSourceFormatting preserves department styling
  • Reduces manual assembly from 3 hours to 5 minutes per report

Industry Use Cases & Applications​

  • 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

Get Help​

Zapier IntegrationGet your API KeyZapier Documentation