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 | Required | What it does | Example |
|---|---|---|---|
| PDF Input Source | Optional | How to provide the PDF files to merge. Options: Add Manually, From Array, All Input Items. Default is `Add Manually`. | Add Manually |
| PDF Files | Conditional | Add multiple PDF files to merge. Each file can use a different input type. Shown when PDF Input Source is Add Manually. | Array of PDFs |
| PDF Array | Conditional | Expression that returns an array of PDFs. Use base64 strings or URLs. E.g. {{ $JSON.pdfArray }}. Shown when PDF Input Source is From Array. | |
| Array Content Type | Conditional | What each element in the array contains. Shown when PDF Input Source is From Array. Options: URLs, Base64 Strings, Objects with URL or Base64. Default is `URLs`. | URLs |
| Binary Property Name | Conditional | Name of the binary property containing the PDF on each input item. Shown when PDF Input Source is All Input Items. Default is `data`. | data |
| Output File Name | Optional | Name for the output merged PDF file. Default is `merged_output.pdf`. | merged_output.pdf |
| Document Name | Optional | Name of the output document for reference. Default is `merged_output`. | merged_output |
| Advanced Options | Optional | Optional settings, collapsed behind Add Option. | Add Option |
| Custom Profiles | Optional | Use "JSON" to adjust custom properties. Review Profiles at https://dev.pdf4me.com/apiv2/documentation/ to set extra options for API calls. | { "outputDataFormat": "base64", "preserveMetadata": true, "optimizeForPrinting": false, "compressionLevel": "medium" } |
| Binary Data Output Name | Optional | Custom name for the binary data in n8n output. Default is `data`. | data |
Output
Output Parameters
| Field | Type | What it contains |
|---|---|---|
fileName | String | File name of the resulting file. |
mimeType | String | MIME type of the resulting file, for example `application/pdf`. |
fileSize | Number | Size of the resulting file in bytes. |
success | Boolean | True when the operation succeeded. |
inputFileCount | Number | Number of PDF files that were merged. |
data | Binary | The merged PDF. With PDF Input Source All Input Items, the node merges all input items and returns a single item. |
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