Split Document - Document Division for Zapier

PDF4me Split Document action enables dividing Word documents into multiple smaller documents within Zapier workflows with flexible splitting options and comprehensive configuration control. This powerful document splitting service supports multiple split types: page-based splitting (all pages individually or custom page ranges), section-based division (split at Word section breaks), and heading-based separation (split at specific heading styles like Heading 1), with unique GUID filenames for each split document, full format preservation, and culture-specific processing—perfect for document management, content distribution, chapter extraction, and workflow automation 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 splitting services.

Get your API Key

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 action. Configure these parameters to control document splitting behavior.

Important: Parameters marked with an asterisk (***) are required and must be provided for the action to function correctly.

Parameter	Type	Description	Example
File Name***	String	Word Document Name • Filename with .docx or .doc extension • Used for reference and processing • Supports dynamic naming from Zap variables • Used for document identification during splitting	`document.docx`
Document***	File	Word File Content • Map from previous step (Drive/Dropbox/HTTP) • Binary Word document to split • Must be valid Word format (.docx, .doc) • Document divided based on specified criteria	`[File]`
Split Type	String	Type 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 Config	String	Configuration 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 Name	String	Document 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
JSON
Zap Integration

Table View

Parameter	Type	Description
documents	Array	Array of split document objects
documents[].Name	String	Generated filename for split document (GUID.docx)
documents[].DocData	File	Individual split document content

JSON Response Format

{
  "documents": [
    {"Name": "12345678-1234-1234-1234-123456789abc.docx", "DocData": "[File]"},
    {"Name": "87654321-4321-4321-4321-cba987654321.docx", "DocData": "[File]"}
  ]
}

Scenario Examples

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

Section Distribution
Chapter Extraction
Page Range Split

Automated Section-Based Distribution Workflow

Complete Scenario Steps:

Trigger: Monthly consolidated report finalized
Get Consolidated Report: Retrieve multi-section report
Split by Sections: Split Type = "section" (Word section breaks)
Iterate Split Docs: Loop through documents array
Rename by Department: Map GUID names to department names
Upload Each Section: Save to respective department folders
Email Departments: Send section to each department head
Archive Full Report: Store complete consolidated version
Log Distribution: Record section distributions
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

Create Zap

Industry Use Cases & Applications

Legal & Professional
Publishing & Documentation
Corporate & Business
Education

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

Zapier Integration Get your API Key Zapier Documentation

Authenticating Your API Request​

Key Features​

Parameters​

Output​

Scenario Examples​

Industry Use Cases & Applications​

Get Help​