Actions19
- AI Invoice Parser
- URL/HTML to PDF
- Merge PDF
- Split PDF
- Convert To PDF
- Convert From PDF
- Add Text/Images to PDF
- Fill a PDF Form
- PDF Information & Form Fields
- Compress PDF
- PDF Security
- Rotate PDF Pages
- Delete PDF Pages
- Search in PDF
- Search & Replace Text or Delete
- Barcode Reader
- Barcode Generator
- Make PDF Searchable or Unsearchable
- Upload File
Overview
This node merges multiple PDF files from given URLs into a single PDF document. It is useful when you have several PDF documents hosted online and want to combine them into one file for easier sharing, archiving, or processing. The node can also automatically convert certain non-PDF file types (like DOC, XLS, JPG, MSG, EML) to PDF before merging, which simplifies workflows involving mixed document formats.
Practical examples:
- Combining multiple invoices or reports hosted on different URLs into a single consolidated PDF.
- Merging scanned images or email messages converted to PDF into one document.
- Automating the creation of a single PDF portfolio from various source files.
Properties
| Name | Meaning |
|---|---|
| Input Link(s) | URLs of the PDF files to merge. Multiple URLs can be provided. |
| Automatically Convert Non-PDF Files | Whether to auto-convert DOC, DOCX, XLS, JPG, PNG, MSG, EML files to PDF before merging. Options: true or false. |
| Advanced Options | A collection of optional settings: |
| File Name | The name of the output merged PDF file. |
| Webhook URL | A callback URL or webhook to receive the output data asynchronously. |
| Output Links Expiration (In Minutes) | How long the output link remains valid before expiring (default 60 minutes). |
| HTTP Username | HTTP username if required to access any of the source URLs. |
| HTTP Password | HTTP password if required to access any of the source URLs. |
| Custom Profiles | JSON string to specify custom API call options or profiles, e.g., { "outputDataFormat": "base64" }. Useful for advanced configuration per API docs. |
Output
The node outputs a JSON object containing information about the merged PDF file. This typically includes:
- A direct link or URL to download the merged PDF.
- Metadata such as file size, expiration time of the link, and possibly base64 encoded content if specified in custom profiles.
If a webhook URL is provided, the output may be delivered asynchronously via that callback instead of immediate response.
No binary data is directly output by the node; instead, it provides links or encoded data representing the merged PDF.
Dependencies
- Requires internet access to fetch PDF files from the provided URLs.
- May require HTTP authentication credentials if source URLs are protected.
- Uses an external PDF processing API service to perform merging and conversion operations.
- Optional webhook endpoint to receive asynchronous results.
- Custom profiles rely on the external API's profile configurations (see https://developer.pdf.co/api/profiles/index.html).
Troubleshooting
- Invalid or inaccessible URLs: Ensure all input URLs are correct and publicly accessible or provide proper HTTP credentials.
- Unsupported file types: Only certain non-PDF files can be auto-converted. Others must be pre-converted to PDF.
- Expired output links: Adjust the expiration time if the default 60 minutes is insufficient.
- Authentication errors: Verify HTTP username and password if accessing protected resources.
- API limits or failures: Check API key validity and usage quotas with the external PDF service provider.
- Malformed custom profiles JSON: Validate JSON syntax carefully to avoid API call errors.
Links and References
- PDF.co API Profiles Documentation - Details on customizing API calls with profiles.
- General PDF merging concepts: combining multiple PDFs into one consolidated document.
- Webhook usage patterns for asynchronous processing.