Processing

PDF Manipulation Nodes Reference

Technical reference for `copyPdf`, `mergePdf`, `splitPdf`, `compressPdf`, `rotatePdf`, `watermarkPdf`, `metadataPdf`, and `flattenPdf`.

Updated 2 min read

Overview

This page covers the PDF file-manipulation nodes that create new PDF artifacts without changing the broader workflow payload model.

Configuration / Settings

NodeKey settingsNotes
copyPdfsuffixAppends a suffix like _copy to the original filename.
mergePdffilename, orderMode, firstFilePattern, patternOperator, patternCaseSensitive, dedupeByName, pageMode, pageRangesSupports deterministic ordering and optional page filters.
splitPdfUI: method, ranges, pageCountThe UI exposes burst, ranges, and fixed-page splits. The underlying API currently supports burst and explicit page selection; fixed-size chunking should be treated as a current limitation.
compressPdfUI: compression levelCompression is routed through the PDF compression service.
rotatePdfangleExecutor also supports a pages field, although the current sidebar only exposes the angle selector.
watermarkPdftextThe sidebar exposes text. The watermark API also supports opacity, font size, color, and position.
metadataPdftitle, author, subject, keywords, creator, producerOnly the first four are exposed in the sidebar today.
flattenPdfannotations, formsAnnotation flattening is limited because pdf-lib only truly flattens forms.

Inputs Expected

  • All covered nodes expect upstream PDF files as Blob[].
  • mergePdf works best with multiple inputs.
  • splitPdf, compressPdf, rotatePdf, watermarkPdf, metadataPdf, and flattenPdf can process one or more PDFs independently.

Variables Exported / Outputs

Output shape for all covered nodes: Blob[]

Notable metadata:

  • copyPdf, mergePdf, and other file-producing nodes store outputFileIds.
  • mergePdf also records the ordered fileIds it used.
  • splitPdf can produce a ZIP-style artifact depending on the split mode and current API path.

Common Use Cases

  • Preserve the original document with copyPdf before destructive edits.
  • Merge uploads into a single package for email or archive steps.
  • Stamp metadata and watermarking before sending a final download.
  • Flatten filled forms before printing or long-term storage.

Edge Cases

  • mergePdf validates regex patterns and page-range syntax before sending the request.
  • splitPdf has an implementation gap between the UI's fixed-size mode and the current API route.
  • flattenPdf can flatten form fields, but annotation flattening is limited by the underlying library.
  • metadataPdf supports more fields than the sidebar currently exposes, so advanced values may need to be set programmatically.