PDF.co API icon

PDF.co API

Generate PDF, extract data from PDF, split PDF, merge PDF, convert PDF. Fill PDF forms, add text and images to pdf and much more with pdf.co!

Actions19

Merge PDF

AI-generated

Overview

This node merges multiple PDF files from provided URLs into a single PDF document. It supports inputting one or more direct file URLs, with an option to automatically convert non-PDF files (such as DOC, DOCX, XLS, JPG, PNG, MSG, EML) to PDF before merging. Users can customize the output file name, set a callback URL to receive the output data, specify output link expiration time, and provide HTTP authentication credentials if required to access the source URLs. This node is useful for automating the consolidation of multiple PDF documents or converting and merging various file types into one PDF, ideal for workflows involving document management, reporting, or archiving.

Use Case Examples

  1. Merging multiple invoice PDFs from different URLs into a single consolidated PDF report.
  2. Automatically converting and merging a mix of DOCX and JPG files into one PDF for easy sharing.
  3. Setting a webhook to receive the merged PDF output for further automated processing.

Properties

Name Meaning
Authentication Method used to authenticate API requests, either via API Key or OAuth2.
File URL(s) to Merge One or more direct URLs of PDF files to be merged. Multiple URLs can be entered separated by commas or added as multiple fields.
Automatically Convert Non-PDF Files Whether to automatically convert supported non-PDF files (DOC, DOCX, XLS, JPG, PNG, MSG, EML) to PDF before merging.
Advanced Options Additional optional settings for the merge operation, including custom output file name, callback URL for receiving output, output link expiration time, HTTP authentication credentials for source URLs, and custom JSON profiles for PDF processing.

Output

JSON

  • url - URL of the merged PDF file output.
  • fileName - Name of the merged PDF file.
  • expiration - Expiration time of the output link in minutes.

Dependencies

  • Requires API authentication via API Key or OAuth2 to access the PDF.co service.

Troubleshooting

  • Ensure all provided URLs are direct links to accessible PDF or supported file types; inaccessible or incorrect URLs will cause errors.
  • If using HTTP authentication for source URLs, verify the username and password are correct.
  • Check that the API key or OAuth2 credentials are valid and have necessary permissions.
  • If auto-conversion is enabled, unsupported file types may fail to convert and merge.
  • Common error messages may include authentication failures, file access errors, or invalid input URLs. Verify inputs and credentials to resolve.

Links

Discussion