Split a Word Document in Zapier

Split Document is a Zapier action by PDF4me that divides a Word file into multiple smaller documents by page, section break, heading style, or a custom page range you define. Trigger it to distribute chapters to reviewers, send report sections to departments, or extract exhibits from a filed contract. The action returns each split as a separate file with a generated filename.

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 →

How Do I Authenticate My 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

Configure the Split Document action: map File and File Name, choose Split Type, set Split Config for page ranges or heading styles, and Culture Name.

The Split Type field accepts five values: allpages, array, numberofpages, section, and headings.

Important Facts You Should Not Miss

Only File is truly required

The screenshot confirms File is the only field carrying an asterisk. File Name, Split Type, Split Config, and Culture Name are all optional, with Split Type defaulting to allpages.

array and numberofpages behave identically

Both split by the page ranges you set in Split Config, such as "1-3,5,7". They are two accepted values for the same page-range behavior, not different features.

Output files get generated GUID filenames

Each split file in the documents array is named with a generated GUID plus .docx, not a name derived from its content or heading text.

Configuration at a Glance

Example configuration from the Zapier interface

The screenshot shows File mapped from a previous step with File Name "abc.docx", Split Type set to "allpages" (one file per page), Split Config left empty since allpages needs no configuration, and Culture Name "en-US".

File

Map from step

Split Type

allpages

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.

Parameters

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

Required in the Zapier UI: File only. File Name, Split Type, Split Config, and Culture Name are all optional. Split Type defaults to allpages if left blank.

Parameter	Required	What it does	Example
File	Required	Word document content, mapped from a previous step using full file content.	[4. File from Step 4]
File Name	Conditional	Filename with .docx or .doc extension, used for output naming.	abc.docx
Split Type	Conditional	How to divide the document: allpages (one page per file, default), array or numberofpages (custom page ranges), section (at Word section breaks), or headings (at a heading style).	allpages
Split Config	Conditional	Page range such as "1-3,4,5-7" when Split Type is array or numberofpages, or a heading style such as "Heading 1" when Split Type is headings. Not needed for allpages or section.	1-3,4,5-7
Culture Name	Conditional	Culture or locale code affecting language and formatting conventions during processing.	en-US

Split Type Values

Value	Behavior
allpages	Splits into individual pages, one page per output file. This is the default.
array	Splits based on the page ranges set in Split Config, such as "1-3,4,5-7".
numberofpages	Same page-range behavior as array, a second accepted value for the same split.
section	Splits at each Word section break, no Split Config value needed.
headings	Splits at each occurrence of the heading style set in Split Config, such as "Heading 1", matched case-insensitively.

What Fields Does the Output Include?

The action returns a documents array with one entry per split file, rather than a single File Url like most other PDF4me Word actions.

Field	Type	What it contains
documents	Array	One entry per split file produced by the action.
documents[].Name	String	Generated GUID-based filename for the split document, such as 12345678-1234-1234-1234-123456789abc.docx.
documents[].DocData	File	The content of that individual split document, map this into the next step per array item.

Typical Setups

Workflow ExamplesCommon Zapier workflow patterns using Split Document.

Distribute report sections by department

1. A trigger fires when a consolidated multi-section report is finalized in Drive.
2. Split Document runs with Split Type set to "section" to divide the report at its existing Word section breaks.
3. A loop step iterates the documents array and emails each section to its department head.

Extract chapters for reviewer distribution

1. A manuscript is marked ready for review, triggering the Zap.
2. Split Document runs with Split Type set to "headings" and Split Config set to "Heading 1", producing one file per chapter.
3. A loop step routes each chapter to the assigned subject-matter reviewer by email.

Separate contract components by page range

1. A signed contract with exhibits is ready for filing, triggering the Zap.
2. Split Document runs with Split Type set to "array" and Split Config set to "1-10,11,12-15" to separate the main contract, cover sheet, and exhibits.
3. Each component is uploaded to its own folder in the document management system.

Practical Tips

Map full file content, not a reference

If File shows "Exists but not shown", pick the mapping option that provides full file content, or the action can fail to process the document.

Loop through the documents array

The output is an array, not a single file. Add a Looping by Zapier step (or an equivalent iteration step) to handle each split file individually.

array and numberofpages are interchangeable

Both split by the page ranges in Split Config using the same syntax. Pick either value, the behavior is identical.

Heading matching is case-insensitive

Split Config values like "Heading 1" for the headings Split Type match the heading style regardless of case.

Output filenames are GUIDs, not content-based

Rename each split file after the split if you need meaningful filenames, the action names them with a generated GUID plus .docx.

Cheat Sheet

Field	Value
Action	Split Document
File	[mapped from previous step, full content]
File Name	abc.docx
Split Type	allpages
Split Config	1-3,5,7 or Heading 1 (when needed)
Culture Name	en-US

Frequently Asked Questions

How do I split a Word document into multiple files in Zapier?+

Add the PDF4me Split Document action to a Zap, map File with full file content, set Split Type to allpages, section, headings, array, or numberofpages, and set Split Config if required. See Microsoft Learn's discussion on creating separate Word documents from a larger one for how this is normally done by hand.

What is the difference between array and numberofpages for Split Type?+

They behave the same way. Both split the document into custom page ranges defined by Split Config, such as "1-3,4,5-7". array and numberofpages are simply two accepted values for the same page-range splitting behavior.

How do I split a Word document by heading instead of by page?+

Set Split Type to headings and Split Config to the heading style you want to split on, such as "Heading 1". The action creates a new file at each occurrence of that heading style, matching case-insensitively.

What filenames do the split output files get?+

Each entry in the documents output array gets a generated GUID-based filename with a .docx extension, such as 12345678-1234-1234-1234-123456789abc.docx, rather than a name derived from the content.

Can I split a Word document by section breaks?+

Yes. Set Split Type to section and the action splits the document at each Word section break, without needing a Split Config value, producing one file per section. See this discussion on splitting a large document into multiple files for common manual approaches this action automates.

Related Actions

Merge Word Documents

The opposite operation, combine multiple Word files into one instead of dividing a single file.

Delete Pages

Remove specific pages outright instead of splitting them into a separate file.

Update Table of Contents

Refresh the TOC in a merged or edited document, a useful step before you split it into distributable pieces.

Same Task on Other Platforms

Split Document in Make

Same operation as a Make module, visual scenarios with cloud-storage triggers.

Split Word Document in n8n

Configure the same document split as a node in a self-hosted or cloud n8n workflow.

Split Document in Power Automate

Microsoft 365 flows with SharePoint, Outlook, and Teams triggers.

Split Document REST API

The raw PDF4me endpoint, for custom backend code or Postman testing.

Industry Use Cases & Applications

Legal & Professional

• 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

Publishing & Documentation

• Chapter Distribution: Split manuscripts into chapters using Heading 1 for reviewer distribution
• Article Extraction: Extract individual articles from journal compilations using sections
• Module Separation: Split training manuals into modules using heading-based splits
• Sample Chapter Creation: Extract specific chapters using page ranges for marketing samples
• Content Licensing: Separate licensable content sections for individual licensing

Corporate & Business

• Report Section Distribution: Split consolidated reports by department using sections
• Proposal Module Distribution: Extract proposal sections for team collaboration using page ranges
• Manual Splitting: Divide user manuals into topic-specific guides using headings
• Policy Distribution: Extract individual policies from policy manuals using Heading 1
• Training Material Division: Split course packs into individual lessons using sections

Education

• Course Material Distribution: Split course packs into assignments using page ranges
• Exam Section Distribution: Divide exams into sections for different proctors
• Syllabus Component Extraction: Split comprehensive syllabi into topic documents using headings
• Student Portfolio Creation: Extract individual student submissions from combined files
• Reading Assignment Division: Split reading packets using page ranges or sections

Get Help

Zapier IntegrationGet your API KeyZapier Documentation