PDF split
Split 1 PDF → N by page count
The PDF split node breaks one large PDF into several smaller ones, by a set number of pages. It is the step for when a single scanned file actually holds many separate documents that need to travel on their own.
How it works
A common example: a scanner produces one giant PDF of a hundred pages that is really twenty separate five-page records. Split cuts it back into the individual documents.
You choose how many pages go in each piece, and the node produces the set of smaller files for the next step to handle.
Common use cases
Real situations where this node earns its place in a flow.
Burst a combined PDF
Break a merged upload into per-document pieces so each can be handled on its own.
Chop into fixed chunks
Split a long file into page-count chunks to process or route separately.
Separate a batch scan
Split a single scan of many applications back into one file each.
PDF split in a workflow
A simple example of where this node sits in a flow.
What you set up
- Connect the large PDF from the step before.
- Set how many pages each split file should contain.
- Each resulting file flows into the next step.
Common questions
Can I split every N pages?
Yes. Set the pages-per-file and the node cuts the document into evenly sized pieces.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
pagesPerFileHow many pages go into each output file; at least 1.
Type: numberDefault:1filenameTemplateNaming pattern for each split output file, where {n} is the part number.
Type: stringDefault:part-{n}.pdf
How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.
{
"id": "split-pdf",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "split-pdf",
"kind": "processor",
"title": "PDF split",
"subtitle": "Split 1 PDF → N by page count",
"config": {
"pagesPerFile": "1",
"filenameTemplate": "part-{n}.pdf"
}
}
}