Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

Compare Word Documents Using Zapier

Compare Documents is a Zapier action by PDF4me that compares an original and a revised Word file and returns a single document with tracked changes, the same output Word's own Compare feature produces, but automated. Ignore formatting, case, comments, tables, or fields to focus the redline. Ideal for contract redlining and version control without opening Word.

Related Blog Posts
No blog post yet for this feature — coming soon.
In the meantime, browse the PDF4me blog for tutorials and workflows across every platform.
Visit the blog →

How Do I Authenticate My API Request?​

To access the PDF4me Web API through Zapier, every request must include proper authentication credentials. Authentication ensures secure communication and validates your identity as an authorized user, enabling seamless integration between your Zapier workflows and PDF4me's powerful Word document comparison services.

Get your API Key
PDF4me Compare Documents Word Zapier - File, File Name, Second Document, Second File Name, Ignore Formatting, Ignore Case Changes, Ignore Comments all set to True
Configure the Compare action, map File and File Name (first document), Second Document and Second File Name (revised); set Ignore Formatting, Ignore Case Changes, Ignore Comments.
Compare Documents Word Zapier - Ignore Comments, Ignore Tables, Ignore Fields, Ignore Footnotes, Ignore Textboxes, Ignore header and footer all set to True, and Author set to Comparison
The remaining Ignore toggles and the optional Author field for tracked-changes attribution.

Important Facts You Should Not Miss​

Only File and Second Document are required
The screenshot confirms both carry asterisks in the Zapier UI. File Name, Second File Name, every Ignore toggle, and Author are optional.
Eight independent Ignore toggles
Formatting, Case Changes, Comments, Tables, Fields, Footnotes, Textboxes, and Headers And Footers can each be ignored independently, so you can focus a redline on exactly the change types that matter.
Both files need full content, not a reference
If File or Second Document shows "Exists but not shown", pick the mapping option that provides the full file content, or the comparison fails.

Configuration at a Glance​

Example configuration from the Zapier interface

File and File Name (first/original) and Second Document and Second File Name (second/revised) mapped from previous steps. Example: File Name = abc.docx, Second File Name = abcd.docx. All eight Ignore toggles set to True, and Author left at the default Comparison.

File

Original (abc.docx)

Second Document

Revised (abcd.docx)

Ignore Formatting

True

Author

Comparison

Parameters​

Complete list of parameters for the Compare Documents action. Parameter names match the Zapier configuration UI.

Required in the Zapier UI: File and Second Document. File Name, Second File Name, every Ignore toggle, and Author are optional.

ParameterRequiredWhat it doesExample
FileRequiredThe original (baseline) document, mapped from a previous step with full file content.abc.docx
File NameConditionalFilename with .docx or .doc extension for the original document.abc.docx
Second DocumentRequiredThe revised document. Changes from this file relative to File are marked in the output.abcd.docx
Second File NameConditionalFilename with extension for the revised document.abcd.docx
Ignore FormattingConditionalTrue skips bold, italic, font, and color differences.True
Ignore Case ChangesConditionalTrue treats "Hello" and "hello" as identical instead of flagging a case change.True
Ignore CommentsConditionalTrue skips comment additions and edits.True
Ignore TablesConditionalTrue skips table structure and content changes.True
Ignore FieldsConditionalTrue skips auto-updating fields such as dates, preventing false positives.True
Ignore FootnotesConditionalTrue skips footnote content changes.True
Ignore TextboxesConditionalTrue skips textbox content and positioning changes.True
Ignore Headers And FootersConditionalTrue skips header and footer content changes, focusing on the document body.True
AuthorConditionalName attributed to the tracked changes in the output document. Defaults to Comparison.Comparison

What Fields Does the Output Include?​

The action returns the comparison document (with tracked changes) plus tracking metadata. This output shape is common across all PDF4me Word file-returning actions in Zapier.

FieldTypeWhat it contains
Job IdStringUnique identifier for the Zapier job execution.
File UrlURLAPI endpoint to download the comparison document. Map this to the next step, Drive, Dropbox, or another PDF4me Word action.
Alternate File UrlURLAlternate download URL with the filename in the path.
File NameStringBase filename without extension.
Full File NameStringComplete filename including extension.
File ExtensionStringFile extension of the output, .docx.

Typical Setups​

Workflow ExamplesCommon Zapier workflow patterns using Compare Documents.
Redline a new contract version
  1. A new contract version lands in a Google Drive contracts folder, triggering the Zap.
  2. Compare Documents runs with File set to the archived baseline contract and Second Document set to the new version, Ignore Formatting and Ignore Fields set to True so the redline focuses on substantive text changes.
  3. Author is set to "Legal Review" and the redline is emailed to the attorneys handling the deal.
Track every change in a policy revision
  1. A policy revision is submitted for review through a SharePoint list.
  2. Compare Documents runs with File set to the current approved policy and Second Document set to the proposed revision, with every Ignore toggle left False for comprehensive tracking.
  3. The comparison is uploaded to the review committee's shared folder.
Build an audit trail across document versions
  1. A scheduled trigger lists all versions of a controlled document from a version-control folder.
  2. Compare Documents runs on each consecutive pair, with Ignore Fields set to True to prevent auto-updating dates from appearing as false changes.
  3. Each comparison is stored in an audit folder as evidence of what changed between versions.

Practical Tips​

Map full file content, not a reference
If File or Second Document shows "Exists but not shown", pick the mapping option that provides full file content, or the comparison fails.
Ignore Fields avoids false positives from dates
Auto-updating fields like today's date will otherwise show up as a change on every comparison run, even when nothing else changed.
Ignore Formatting isolates substantive edits
Turn this on when reviewers only care about wording changes, not font, color, or bold/italic differences between versions.
Author labels the tracked changes
Set Author to a reviewer name or team label, such as "Legal Review", so the redline shows who or what generated the comparison.
Leave all Ignore toggles False for a full audit
A comprehensive comparison with every toggle False is noisier to read but is the right choice for compliance or audit trail use cases.

Cheat Sheet​

FieldValue
ActionCompare Documents
File[mapped, original document]
File Nameabc.docx
Second Document[mapped, revised document]
Second File Nameabcd.docx
Ignore FormattingTrue
Ignore Case ChangesTrue
Ignore FieldsTrue
AuthorComparison

Frequently Asked Questions​

How do I compare two Word documents automatically in Zapier?+
Add the PDF4me Compare Documents action to a Zap, map File to the original document and Second Document to the revised one, both with full file content, choose which change types to ignore, and run the Zap. See Microsoft's guide to comparing documents for background on how Word's own comparison feature works.
Can I ignore formatting changes and only track content edits?+
Yes. Set Ignore Formatting to True to skip bold, italic, font, and color differences and focus the redline on substantive text changes only.
Does the comparison work like Word's built-in Compare feature?+
Yes, the output is a tracked-changes document similar to what Word's Review > Compare produces, but generated automatically inside a Zap without opening Word.
Can I attribute the tracked changes to a specific reviewer?+
Yes. Set Author to a name or a value mapped from a previous step, such as a reviewer's name or a team label. It defaults to Comparison if left blank.
What happens if I leave all the Ignore options set to False?+
The comparison tracks every difference, including formatting, case, comments, tables, fields, footnotes, textboxes, and headers/footers, producing the most complete but also the noisiest redline. See Attorney at Work's guide to redlining legal drafts for how legal teams typically scope a comparison.

Same Task on Other Platforms​

Industry Use Cases & Applications​

  • Contract Redlining: Compare contract drafts showing all negotiation changes with tracked revisions
  • Legal Brief Versions: Compare brief drafts tracking argument and citation modifications
  • Settlement Agreement Review: Compare settlement versions identifying all negotiated changes
  • Court Filing Comparison: Compare filed vs draft documents ensuring accuracy before filing
  • Client Document Review: Compare client-submitted vs firm-revised documents showing recommendations

Get Help​

Zapier IntegrationGet your API KeyZapier Documentation