Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

Split Word Document using n8n action

PDF4me Split Word Document enables dividing Word documents into multiple smaller documents through n8n automation workflows with flexible splitting options and comprehensive configuration control. This powerful document splitting feature supports page-based splitting, section-based division, heading-based separation, and custom page ranges with full control over split criteria, document naming, and output organization, perfect for document management, content distribution, and workflow automation.

Setup​

Add the PDF4me "Split Word Document" node to your n8n workflow and configure the required parameters. For initial setup instructions, see our n8n Integration Guide.

Prerequisites:

  • PDF4me API credentials
  • n8n workflow access
Get Your API Key

Configuration:

  1. Add PDF4me node to workflow
  2. Select "Split Word Document" action
  3. Configure input parameters (see below)
Split Word Document

Parameters​

Complete list of parameters for the Split Word Document action. Configure these parameters to control document splitting behavior.

Important: Parameters marked with an asterisk (***) are required. Advanced parameters provide fine-grained control over splitting criteria and document processing.

ParameterTypeDescriptionExample
Input Data Type***StringWord Document Input Format Selection
• Choose the format of your Word document data input
• PDF4me supports multiple input types
• Options: Binary Data, Base64 String, or URL		Binary Data
Input Binary Field***BinaryBinary Word File Input (Required if Binary Data)
• Reference Word file (.docx, .doc) from previous n8n node or file upload
• PDF4me processes binary Word files with automatic format detection
• Required when Input Data Type is "Binary Data"		{{ $binary.data }}
Base64 Word Content***StringBase64 Encoded Word Input (Required if Base64 String)
• Provide Word content (.docx, .doc) as base64 encoded string for secure transmission
• PDF4me automatically decodes and processes the Word content
• Required when Input Data Type is "Base64 String"		UEsDBBQABgAI...
Word Document URL***StringPublic Word Document URL Input (Required if URL)
• Provide a public/open permission URL to the Word file (.docx, .doc) to be processed
• PDF4me downloads and processes the Word file from the provided URL
• Required when Input Data Type is "URL"		https://abc.com/document.docx
Word Document Name***StringWord Document Input Filename
• Specify the name of the input Word file with proper extension (.docx, .doc)
• PDF4me uses this for format detection and processing optimization		document.docx
Split TypeStringType of Document Splitting
• allpages - Split into individual pages (default)
• array - Split based on page ranges (e.g., "1-3,4,5-7")
• numberofpages - Split based on page ranges (same as "array")
• section - Split by document sections
• headings - Split by heading styles (e.g., "Heading 1")		"allpages"
Split ConfigStringConfiguration for Splitting
• Page Ranges: "1-3,4,5-7" (pages 1-3, page 4, pages 5-7)
• Single Pages: "1,3,5" (pages 1, 3, and 5)
• Heading Styles: "Heading 1" or "Heading 2"
• Required when Split Type is "array", "numberofpages", or "headings"		"1-3,4,5-7"
Culture NameStringDocument Culture/Locale
• Culture code for document processing (e.g., "en-US", "de-DE", "fr-FR")
• Default: "en-US"
• Affects document language and formatting		en-US

Output​

Output Parameters​

ParameterTypeDescriptionExample
fileNameStringSplit document filename - The name of the output split Word document filedocument_part1.docx
fileSizeNumberFile size in bytes - The size of the split Word document in bytes13398
partNumberNumberPart number - The sequential number of this split part (1-based)1
totalPartsNumberTotal number of parts - The total number of split parts created from the original document1
successBooleanPDF4me operation status - Boolean flag indicating the success or failure of the document splitting operation. PDF4me returns true for successful operations and false for any errorstrue
originalFileNameStringOriginal Word document filename - The name of the input Word document filedocument.docx
splitTypeStringSplit type used - The type of splitting that was applied (e.g., "Pages", "Sections", "Headings")Pages
pageRangesStringPage ranges - The page ranges that were used for splitting (e.g., "1,2,3" or "1-3,4,5-7")1,2,3
cultureNameStringDocument culture/locale - The culture code used for document processing (e.g., "en-US", "de-DE", "fr-FR")en-US
messageStringOperation message - Descriptive message indicating the result of the splitting operation, including part informationSplit document part 1 of 1

N8N Action Response​

The PDF4me Split Word Document API returns a response that can be viewed in multiple formats. Choose the view that best fits your needs:

JSON Response Format

The raw JSON response from the API:

[
  {
    "fileName": "document_part1.docx",
    "fileSize": 13398,
    "partNumber": 1,
    "totalParts": 1,
    "success": true,
    "originalFileName": "document.docx",
    "splitType": "Pages",
    "pageRanges": "1,2,3",
    "cultureName": "en-US",
    "message": "Split document part 1 of 1"
  }
]

Use Cases​

Enterprise Document Automation​

  • Document Management: Divide large documents into manageable sections
  • Content Distribution: Split documents for targeted distribution
  • Workflow Automation: Process document sections separately
  • Archive Management: Organize documents by splitting into logical sections

AI-Powered Document Processing​

  • Multi-Format Support: Process Word documents in .docx and .doc formats
  • Multi-Language Processing: Support for different languages and regions
  • Intelligent Splitting: Automatic splitting based on document structure

Business Intelligence and Analytics​

  • Document Organization: Organize documents with proper structure
  • Content Management: Manage content by splitting into logical units
  • Performance Metrics: Track processing accuracy and efficiency

Get Help​

n8n Integration Guiden8n SampleGetting Started