PDF merge
Combine N filled PDFs → 1
The PDF merge node combines several PDFs into a single file, in order. It is the step that takes a set of separate documents and staples them into one clean deliverable.
How it works
It is the natural partner to steps that produce many files, like PDF fill (one form per row) or a batch of reports. Merge gathers them into a single document to send or store.
The files are combined in the order they arrive, so the finished PDF reads the way you expect.
Common use cases
Real situations where this node earns its place in a flow.
Combine filled forms
After filling many PDFs, merge them into a single packet ready to send or file.
Staple report to sources
Join a generated report with the original documents into one download.
One PDF per applicant
Merge everything produced for a case into a single file for the record.
PDF merge in a workflow
A simple example of where this node sits in a flow.
What you set up
- Connect the multiple PDFs from the step before.
- They combine in order into one file.
- Send or store the merged result.
Common questions
What order do the pages end up in?
The files are joined in the order they come into the node, so the result follows the sequence of the step feeding it.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
filenameTemplateOutput filename for the merged PDF; a .pdf extension is appended if absent.
Type: stringDefault:merged.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": "pdf-merge",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "pdf-merge",
"kind": "processor",
"title": "PDF merge",
"subtitle": "Combine N filled PDFs → 1",
"config": {
"filenameTemplate": "merged.pdf"
}
}
}