Actions80
- Add Attachment To PDF
- Add Barcode To PDF
- Add Form Fields To PDF
- Add HTML Header Footer
- Add Image Stamp To PDF
- Add Image Watermark To Image
- Add Margin To PDF
- Add Page Number To PDF
- Add Text Stamp To PDF
- Add Text Watermark To Image
- AI-Invoice Parser
- AI-Process Contract
- AI-Process HealthCard
- Classify Document
- Compress Image
- Compress PDF
- Convert HTML To PDF
- Convert Image Format
- Convert JSON To Excel
- Convert Markdown To PDF
- Convert PDF To Editable PDF Using OCR
- Convert PDF To Excel
- Convert PDF To PowerPoint
- Convert PDF To Word
- Convert To PDF
- Convert URL to PDF
- Convert VISIO
- Convert Word to PDF Form
- Create Images From PDF
- Create PDF/A
- Create Swiss QR Bill
- Crop Image
- Delete Blank Pages From PDF
- Delete Unwanted Pages From PDF
- Split PDF By Barcode
- Disable Tracking Changes In Word
- Enable Tracking Changes In Word
- Extract Attachment From PDF
- Extract Form Data From PDF
- Extract Pages From PDF
- Extract Resources
- Extract Table From PDF
- Extract Text By Expression
- Extract Text From Word
- Fill PDF Form
- Find And Replace Text
- Flip Image
- Flatten PDF
- Generate Barcode
- Generate Document Single
- Generate Documents Multiple
- Get Document From Pdf4me
- Get Image Metadata
- Get PDF Metadata
- Split PDF By Swiss QR
- Get Tracking Changes In Word
- Image Extract Text
- Linearize PDF
- Merge Multiple PDFs
- Overlay PDFs
- Parse Document
- Protect PDF
- Read Barcode From Image
- Read Barcode From PDF
- Read SwissQR Code
- Remove EXIF Tags From Image
- Repair PDF Document
- Replace Text With Image
- Replace Text With Image In Word
- Resize Image
- Rotate Document
- Rotate Image
- Rotate Image By EXIF Data
- Rotate PDF Page
- Sign PDF
- Split PDF By Text
- Split PDF Regular
- Unlock PDF
- Update Hyperlinks Annotation
- Upload File To PDF4me
Overview
This node operation merges multiple PDF files into a single PDF document. It is useful when you have several separate PDF documents that need to be combined into one cohesive file for easier sharing, archiving, or processing. For example, merging invoices, contracts, reports, or scanned documents into one consolidated PDF.
The node supports different ways to provide the input PDFs: as binary data from previous nodes, base64 encoded strings, or URLs pointing to the PDF files. After merging, it outputs the combined PDF as binary data, which can then be used in subsequent workflow steps such as saving to storage, sending via email, or further processing.
Properties
| Name | Meaning |
|---|---|
| PDF Files | Collection of multiple PDF files to merge. Each file can be provided as: - Binary Data (from previous nodes) - Base64 encoded string - URL to the PDF file. Also allows specifying an optional file name for reference. |
| Output File Name | The desired file name for the merged output PDF file (e.g., "merged_document.pdf"). |
| Document Name | A reference name for the output document (e.g., "merged-document"). |
| Advanced Options | Optional JSON string to specify custom profiles and additional settings for the merge operation. This allows advanced users to tweak API call properties according to external documentation. |
| Binary Data Output Name | Custom name for the binary property in the node's output where the merged PDF binary data will be stored (default is "data"). |
Output
The node outputs the merged PDF file as binary data under the specified binary data output name (default "data"). The output JSON also includes metadata such as the document name and file name for reference. This binary data can be directly used by other nodes that accept binary inputs, such as file storage or email sending nodes.
Dependencies
- Requires an active connection to the PDF processing service API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node relies on the external PDF4me API for merging functionality.
- Users may optionally configure advanced options using JSON profiles as per the PDF4me API documentation.
Troubleshooting
- Common issues:
- Providing invalid or inaccessible URLs for PDF files will cause failures.
- Incorrect base64 content format or corrupted binary data will result in errors.
- Missing or invalid API authentication will prevent the merge operation.
- Error messages:
- Errors related to file retrieval usually indicate network or URL issues.
- API errors about invalid input typically mean the PDF content was malformed.
- Authentication errors require checking the configured API credentials.
- Resolutions:
- Verify all input PDF sources are accessible and correctly formatted.
- Ensure the API key/token is valid and has necessary permissions.
- Use the advanced options carefully; incorrect JSON syntax can cause failures.
Links and References
- PDF4me API Documentation
- n8n Documentation on Working with Binary Data
- General guide on Merging PDFs