Skip to main content

Split Document - Document Division for Zapier

PDF4me Split Document divides a Word file into multiple smaller documents—by pages (one per file or custom ranges like "1-3,5,7"), by sections (at section breaks), or by headings (at Heading 1, Heading 2). Each split gets a unique GUID filename. Ideal for distributing chapters, sending sections to different recipients, or breaking large reports into manageable pieces.

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 splitting services.

PDF4me Split Document Word Zapier - File, File Name, Split Type, Split Config
Configure the Split action—map File, File Name; set Split Type (allpages, section, headings, array) and Split Config for page ranges or heading styles.
Split Document Word Zapier - Culture Name
Optional—Culture Name for locale-specific processing.

Configuration at a Glance

Example configuration from the Zapier interface

File and File Name mapped from previous step; Split Type = allpages (one page per file) or section (split at section breaks) or headings with Split Config = "Heading 1"; for page ranges use Split Type = array and Split Config = "1-3,5,7".

File

Map from step

Split Type

allpages/section/headings

Split Config

1-3,5,7 or Heading 1

Culture Name

en-US

Map File from previous steps

Use the + button to map File and File Name from earlier Zap steps. The Word file must provide full content, not "Exists but not shown".

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.

Key Features

  • Multiple Split Types: Split by pages, sections, headings, or custom ranges
  • Page Range Support: Split based on specific page numbers or ranges
  • Section-Based Splitting: Divide documents by Word sections
  • Heading-Based Division: Split at specific heading styles (Heading 1, 2, etc.)
  • Flexible Configuration: Custom split criteria with Split Config parameter
  • Unique Document Names: Each split document gets a unique GUID filename
  • Format Preservation: Maintains original document formatting and structure
  • Culture Support: Locale-specific document processing

Parameters

Complete list of parameters for the Split Document action. Parameter names match the Zapier configuration UI.

Quick setup checklist
  1. Map File and File Name from previous step
  2. Set Split Type: allpages (one per page), section (section breaks), headings, or array (page ranges)
  3. For array/headings: set Split Config (e.g., "1-3,5,7" or "Heading 1")
  4. Set Culture Name if needed (default en-US)

Important: Parameters marked with an asterisk (***) are required.

ParameterTypeDescriptionExample
File***FileWord document—map from previous step (Drive, Dropbox, trigger)[4. File from Step 4]
File NameStringWord filename—with .docx or .doc extensiondocument.docx
Split TypeStringType of Document Splitting
"allpages" - Split into individual pages (one page per file, default)
"array" - Split based on page ranges from Split Config
"numberofpages" - Split based on page ranges (same as "array")
"section" - Split by document sections (Word section breaks)
"headings" - Split by heading styles specified in Split Config
• Controls how document is divided
• Each split document gets unique GUID filename
• Preserves formatting and structure
allpages
Split ConfigStringConfiguration for Splitting
For Page Ranges (Split Type = "array" or "numberofpages"):
- Format: "1-3,4,5-7" (pages 1-3, page 4, pages 5-7)
- Single pages: "1,3,5" (pages 1, 3, and 5)
- 1-based page numbering
For Heading-Based (Split Type = "headings"):
- Format: "Heading 1" or "Heading 2"
- Case-insensitive heading style matching
- Splits at each occurrence of specified heading
• Required when Split Type is "array", "numberofpages", or "headings"
• Validates page ranges against document page count
1-3,4,5-7
Culture NameStringDocument Culture/Locale
• Culture code for document processing
• Examples: "en-US", "de-DE", "fr-FR"
• Default: "en-US"
• Affects document language and formatting
en-US

Output

The PDF4me Split Document action returns comprehensive output data for seamless Zapier workflow integration:

Table View

ParameterTypeDescription
documentsArrayArray of split document objects
documents[].NameStringGenerated filename for split document (GUID.docx)
documents[].DocDataFileIndividual split document content

Scenario Examples

The PDF4me Split Document action in Zapier provides comprehensive scenario templates:

Automated Section-Based Distribution Workflow

Complete Scenario Steps:

  1. Trigger: Monthly consolidated report finalized
  2. Get Consolidated Report: Retrieve multi-section report
  3. Split by Sections: Split Type = "section" (Word section breaks)
  4. Iterate Split Docs: Loop through documents array
  5. Rename by Department: Map GUID names to department names
  6. Upload Each Section: Save to respective department folders
  7. Email Departments: Send section to each department head
  8. Archive Full Report: Store complete consolidated version
  9. Log Distribution: Record section distributions
  10. Update Tracking: Mark report as distributed

Business Benefits:

  • Distributes 12 monthly reports to 8 departments automatically
  • Section-based splitting preserves formatting
  • Targeted delivery reduces information overload
  • Eliminates manual section extraction saving 2 hours monthly

Industry Use Cases & Applications

  • Exhibit Extraction: Split exhibits from briefs using page ranges for separate exhibit filing
  • Discovery Distribution: Split document productions by custodian or issue using sections
  • Contract Component Separation: Extract signature pages, schedules, exhibits using page ranges
  • Pleading Division: Split combined pleadings into individual documents for docketing
  • Clause Library Creation: Extract standard clauses from master documents using heading splits

Get Help