PDF diff
Compare 2 PDFs → text redline
Compares two versions of a document and lays out what changed between them as a text redline, like tracked changes, so you can spot edits between a draft and a final.
How it works
Feed it two PDFs, an earlier version and a later one, and it reports the differences in the text: what was added, what was removed, what moved. No more reading both side by side hunting for a single altered clause.
The result is a redline, the familiar marked-up view where changes are called out, so a reviewer can see at a glance whether a returned contract matches the copy that was sent.
It is built for catching quiet edits: a payment term nudged, a date changed, a paragraph slipped in. That makes it useful any time a document leaves your hands and comes back.
Common use cases
Real situations where this node earns its place in a flow.
See what changed
Compare two versions of a contract and get a redline of the differences between them.
Spot altered documents
Diff a resubmitted file against the original to catch changes that should not be there.
Track edits over time
Compare this month's document to last month's to see what moved.
PDF diff in a workflow
A simple example of where this node sits in a flow.
What you set up
- Provide the two PDFs to compare (the original and the revised copy).
- Make sure both are the versions you actually want checked against each other.
- Send or store the redline output so the differences are on record.
Common questions
Does it compare the text or how the page looks?
It focuses on the text content, reporting added, removed, and changed wording. It is meant for catching edits to what a document says, not small shifts in layout.
What if the two files are wildly different?
It still reports the differences, but a redline is most useful between two versions of the same document. Comparing unrelated files produces a lot of noise.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
This node has no configurable settings. Drop it into a flow and it works from its inputs alone.
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-diff",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "pdf-diff",
"kind": "processor",
"title": "PDF diff",
"subtitle": "Compare 2 PDFs → text redline"
}
}