Actions108
- AI Actions
- Transcribe
- Detect Brand
- Extract Contact Information
- Mood Detection
- Detect Adult Content
- Enitity Detection
- Language Detection
- Too Long To Read
- Check Content Policy
- Detect Faces
- Generate Python Code
- Picture Text Recognition
- Detect Color
- Generate Image
- PDF OCR
- Translation
- Detect Email Type
- Generate Javascript Code
- Picture Object Recognition
- Business Actions
- Calculate Actions
- Code Actions
- Convert Actions
- Crypto Actions
- Date & Time Actions
- Generate Actions
- Image Actions
- Operator Actions
- PDF Actions
- Storage Actions
- Text Actions
- User Actions
Overview
The node provides a versatile set of no-code utilities grouped under various resources, including PDF operations. Specifically, the PDF Merge operation allows users to combine multiple PDF files into a single PDF document. This is useful in scenarios where you have several separate PDFs (e.g., reports, invoices, contracts) and want to consolidate them into one file for easier sharing, archiving, or further processing.
For example, a user might merge monthly sales reports from different regions into a single comprehensive report or combine multiple scanned documents into one PDF for client delivery.
Properties
| Name | Meaning |
|---|---|
| Files to Merge | A collection of PDF files to merge. Each entry includes: |
| - File Url or Binary Data | The source PDF file, provided either as a URL or raw binary data. |
| - Page Ranges | Optional page ranges specifying which pages to include from each PDF. Multiple ranges can be specified per file. |
| Get File as URL | Boolean flag indicating whether the merged PDF should be returned as a URL (true) or as raw binary data (false). |
| Code Variables | (Not directly related to PDF Merge) Allows defining variables used in code editor functions, with variable name/ID and value. |
Output
The output JSON contains the result of the merge operation. It typically includes the merged PDF either as:
- A URL pointing to the merged PDF file if "Get File as URL" is true.
- Raw binary data representing the merged PDF if "Get File as URL" is false.
This enables downstream nodes or workflows to access the combined PDF either by downloading it via URL or processing the binary content directly.
Dependencies
- Requires an API key credential for authentication with the external service providing the PDF utilities.
- The node relies on an external API endpoint that performs the actual PDF merging.
- No additional environment variables are explicitly required beyond the API key credential.
Troubleshooting
- Invalid file URLs or corrupted binary data: Ensure that the input PDF files are accessible and valid. Invalid URLs or corrupted data will cause the merge to fail.
- Page range errors: Specifying invalid page ranges (e.g., start page greater than end page, pages outside the document length) may cause errors or unexpected results.
- API authentication errors: Missing or incorrect API credentials will prevent the node from executing successfully.
- Large file sizes: Merging very large PDFs or many files may lead to timeouts or memory issues depending on the external service limits.
If the node throws errors related to file access or API calls, verify the input parameters and credentials first.
Links and References
- n8n Expressions Documentation — For using expressions in variable definitions.
- General PDF merging concepts: https://en.wikipedia.org/wiki/PDF#Merging_and_splitting_PDFs