0-CodeKit icon

0-CodeKit

A toolbox of no-code utilities

Actions40

Overview

The PDF Merge operation in the "0-CodeKit" n8n node allows users to combine multiple PDF files into a single document. This is useful for scenarios such as:

  • Merging several reports, invoices, or forms into one file for easier sharing or archiving.
  • Combining selected pages from different PDFs (e.g., extracting and merging only relevant sections).
  • Automating document assembly workflows.

Practical examples:

  • A business process that collects signed contracts from various sources and merges them into a single archive.
  • An HR workflow that combines onboarding documents for each new employee.

Properties

Name Meaning
Files to Merge Collection of files to be merged. Each entry includes:
- File Url or Binary Data: The source of the PDF, either as a URL or raw binary data.
- Page Ranges: (Optional) Specify which pages to include by start and end page numbers.
Get File as URL Whether the resulting merged PDF should be returned as a downloadable URL (true) or as binary data within the workflow (false).

Output

  • If Get File as URL is true:

    • The output JSON will contain a field with the URL where the merged PDF can be downloaded.

  • If Get File as URL is false:

    • The output will contain the merged PDF as binary data, typically accessible via the n8n binary property system.

Example output (as URL):

{
  "url": "https://example.com/merged.pdf"
}

Example output (as binary):

  • The binary data will be attached to the item under a binary property (e.g., data), not directly visible in the JSON but available for downstream nodes.

Dependencies

  • External Service: Requires access to the CodeKit API (credentials named codeKitApi must be configured in n8n).
  • n8n Configuration: The node must be set up with valid API credentials for CodeKit.

Troubleshooting

Common issues:

  • Invalid file input: If the provided file URLs are inaccessible or the binary data is malformed, the merge may fail.
  • Incorrect page ranges: Specifying invalid or out-of-bounds page numbers can cause errors.
  • API credential errors: Missing or incorrect codeKitApi credentials will prevent the node from functioning.

Error messages and resolutions:

  • "error: Invalid PDF file": Check that all input files are valid PDFs and accessible.
  • "error: Authentication failed": Ensure the codeKitApi credentials are correctly set up in n8n.
  • "error: Page range out of bounds": Verify that the specified start and end pages exist in the source PDFs.

Links and References

Discussion