Merge Multiple PDFs using n8n action
PDF4me Merge Multiple PDFs combines multiple PDF documents into a single unified PDF file through n8n automation workflows. Process PDFs via n8n triggers, binary data, base64 strings, or public URLs to merge documents in specified order with preserved formatting, maintained page structure, bookmarks retention, and seamless consolidation of all content. This solution is ideal for document consolidation, report compilation, multi-source document combining, contract bundling, archive creation, and automated PDF merging workflows that require reliable multi-document combination with preserved quality and seamless integration.
Setup
Add the PDF4me "Merge Multiple PDFs" 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
Configuration:
- Add PDF4me node to workflow
- Select "Merge Multiple PDFs" action
- Configure input parameters (see below)

Parameters
Complete list of parameters for the Merge Multiple PDF files into Single PDF action. Configure these parameters to control PDF merging.
Important: Parameters marked with an asterisk (***) are required and must be provided for the action to function correctly.
| Parameter | Type | Description | Example |
|---|---|---|---|
| PDF Files*** | Array | Input PDF Collection • Collection of PDF files to be merged into a single document • Each file can be provided as binary data, base64 string, or URL • Support for multiple input formats | Array of PDFs |
| Input Type*** | String | Input Format Selection • Choose the format for each PDF file input • PDF4me supports multiple input types for flexible processing • Options: Binary Data, Base64 String, or URL | Binary Data |
| Binary Property Name | String | Binary Data Reference (Required if Binary Data) • Specify the property name for accessing binary PDF data • Should match the binary data property name in your workflow • Required when Input Type is "Binary Data" | data |
| Base64 Document Content | String | Base64 Encoded PDF Input (Required if Base64 String) • Provide PDF data as base64 encoded string • PDF4me automatically decodes and processes the PDF content • Required when Input Type is "Base64 String" | UEsDBBQABgAI... |
| File URL | String | Public PDF URL Input (Required if URL) • Provide a public/open permission URL to the PDF file • PDF4me downloads and processes the file from the provided URL • Required when Input Type is "URL" | https://abc.com/sample.pdf |
| Output File Name*** | String | Merged PDF Output Filename • Specify the name for the generated merged PDF file • Must include .pdf extension • PDF4me ensures unique naming and format validation | merged_output.pdf |
| Document Name*** | String | Document Reference • Specify a reference name for the merged document • Used for tracking and identification purposes • Helps with workflow organization | merged_output |
| Binary Data Output Name*** | String | Binary Data Mapping • Define the variable name for accessing generated merged PDF binary data • Used in subsequent workflow actions • Essential for workflow data flow | data |
Advanced Options
The following parameters are available in the Advanced Options section and are optional:
| Parameter | Type | Description | Example |
|---|---|---|---|
| Custom Profiles | String | No | PDF4me custom configuration profiles - Set additional options for the PDF4me Merge Multiple PDFs operation using custom profiles. A custom profile is a string in JSON-like format containing predefined parameters for advanced merge settings. Supports options like outputDataFormat, preserveMetadata, optimizeForPrinting, compressionLevel, and colorSpaceOptimization |
Output
Output Parameters
| Parameter | Type | Description | Example |
|---|---|---|---|
| fileName | String | PDF4me generated merged PDF filename - The complete filename of the successfully generated merged PDF document with proper .pdf extension. PDF4me ensures unique naming and validates file format compliance for seamless integration with downstream processes | merged_output.pdf |
| mimeType | String | PDF4me output MIME type - MIME type of the generated PDF file, always "application/pdf" for PDF documents. Useful for content type validation and proper file handling in web applications | application/pdf |
| fileSize | Number | PDF4me merged PDF file size in bytes - The exact size of the generated merged PDF file in bytes, provided by PDF4me for storage planning, bandwidth optimization, and file transfer monitoring. Essential for enterprise document management and workflow automation | 5417 |
| success | Boolean | PDF4me merge operation status indicator - Boolean flag indicating the success or failure of the PDF merge process. PDF4me returns true for successful operations and false for any errors, enabling robust error handling in automated workflows | true |
| inputFileCount | Number | PDF4me input files processed count - The number of individual PDF files that were successfully processed and merged into the final document. Useful for verifying that all intended files were included in the merge operation | 2 |
N8N Action Response
The PDF4me Merge Multiple PDFs API returns a response that can be viewed in multiple formats. Choose the view that best fits your needs:
- JSON
- Table
- Schema
- Binary
JSON Response Format
The raw JSON response from the API:
[
{
"fileName": "merged_output.pdf",
"mimeType": "application/pdf",
"fileSize": 5417,
"success": true,
"inputFileCount": 2
}
]
Table View
Response data in a structured table format:
| Parameter | Value |
|---|---|
| fileName | merged_output.pdf |
| mimeType | application/pdf |
| fileSize | 5417 |
| success | true |
| inputFileCount | 2 |
Schema View
The data structure and types of the response:
1 item
fileName: AB merged_output.pdf
mimeType: AB application/pdf
fileSize: # 5417
success: ☑ true
inputFileCount: # 2
Type Indicators:
AB= String#= Number☑= Boolean
Binary Data View
The actual merged PDF file data and metadata:
data
─────────────────────────────
File Name: merged_output.pdf
File Extension: pdf
Mime Type: application/pdf
File Size: 5.3 KB
Binary Data Access:
- n8n Binary Object:
$binary.data.data - Base64 Content: Available for direct use
- File Operations: Ready for download, email, or storage
Use Cases
Document Consolidation and Archiving
- Combine multiple related PDF documents into a single comprehensive file for easier storage and management
- Merge quarterly reports, invoices, or contracts into organized collections for archival purposes
- Consolidate scattered documents from different sources into unified project files
Report Generation and Compilation
- Automatically merge individual report sections from different team members into a complete final report
- Combine data exports, charts, and analysis documents into comprehensive business reports
- Create unified documentation packages by merging related technical specifications and user guides
Workflow Automation and Batch Processing
- Automate the merging of daily, weekly, or monthly document batches in enterprise workflows
- Combine multiple form submissions or applications into consolidated processing files
- Merge related documents from different departments or systems into unified records for compliance and auditing