Compare Documents - Version Control for Zapier

PDF4me Compare Documents action enables comparing two Word documents and tracking changes with comprehensive comparison options within Zapier workflows. This powerful document comparison service supports detailed change tracking, customizable comparison settings for formatting/case/comments/tables/fields/footnotes/textboxes/headers-footers, revision management with automatic cleanup, author attribution for tracked changes, and professional comparison report generation—perfect for document review, version control, collaborative editing, contract redlining, and legal document comparison workflows across cloud storage platforms and business applications.

Authenticating Your 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

Key Features

• Document Comparison: Compare two Word documents and identify all differences
• Track Changes: Generate documents with tracked changes showing modifications
• Customizable Options: Control what types of changes to track or ignore
• Revision Management: Clean up existing revisions before comparison
• Author Attribution: Assign changes to specific authors for accountability
• Professional Output: Generate clean comparison documents with revision tracking
• Multiple Format Support: Compare .docx and .doc files
• Advanced Filtering: Ignore formatting, case changes, comments, tables, and more

Parameters

Complete list of parameters for the Compare action. Configure these parameters to control document comparison behavior.

Important: Parameters marked with an asterisk (***) are required and must be provided for the action to function correctly.

Parameter	Type	Description	Example
First Document Name***	String	Base Document Name • Name of the first (original/base) document • Used for reference and processing • Must include file extension (.docx, .doc) • This document serves as comparison base	original.docx
First Document Content***	File	Base Document Content • Binary content of the first document • Map from previous step (Drive/Dropbox/HTTP) • Must be valid Word format • Serves as baseline for comparison	[File]
Second Document Name***	String	Modified Document Name • Name of the second (revised) document • Used for reference and processing • Must include file extension (.docx, .doc) • This document is compared against first	modified.docx
Second Document Content***	File	Modified Document Content • Binary content of the second document • Map from previous step (Drive/Dropbox/HTTP) • Must be valid Word format • Changes from this document marked in output	[File]
Ignore Formatting	Boolean	Ignore Formatting Changes • Yes - Ignore formatting (bold, italic, font, color) • No - Track formatting changes (default) • Useful when only content changes matter	No
Ignore Case Changes	Boolean	Ignore Case Changes • Yes - Ignore case ("Hello" vs "HELLO") • No - Track case changes (default) • Treats "Hello" and "hello" as identical when Yes	No
Ignore Comments	Boolean	Ignore Comments • Yes - Ignore comment changes and additions • No - Track comment changes (default) • Focuses comparison on document content only	No
Ignore Tables	Boolean	Ignore Table Changes • Yes - Ignore table structure and content changes • No - Track table changes (default) • Focuses on text content only when Yes	No
Ignore Fields	Boolean	Ignore Field Changes • Yes - Ignore field updates (dates, formulas) • No - Track field changes (default) • Prevents false positives from auto-updating fields	No
Ignore Footnotes	Boolean	Ignore Footnote Changes • Yes - Ignore footnote content changes • No - Track footnote changes (default) • Focuses on main document content when Yes	No
Ignore Textboxes	Boolean	Ignore Textbox Changes • Yes - Ignore textbox content and positioning • No - Track textbox changes (default) • Focuses on main document flow when Yes	No
Ignore Headers And Footers	Boolean	Ignore Header/Footer Changes • Yes - Ignore header and footer content • No - Track header/footer changes (default) • Focuses on document body when Yes	No
Author	String	Comparison Author Name • Author name for tracked changes • Default: "Comparison" • Attributes changes in result document • Can be dynamic from Zap variables	John Doe

Output

The PDF4me Compare Documents action returns comprehensive output data for seamless Zapier workflow integration:

Table

Table View

Response data in a structured table format:

Parameter	Type	Description
File	URL	Direct URL to access the comparison result document
File Name	String	The filename without extension
Full File Name	String	Complete filename with .docx extension
File Extension	String	File extension (.docx)

JSON

JSON Response Format

The raw JSON response from the action:

{
  "File": "https://...",
  "File Name": "comparison_result",
  "Full File Name": "comparison_result.docx",
  "File Extension": ".docx"
}

Zap Integration

Zapier Workflow Usage

Use comparison documents in subsequent modules:

• Review Distribution: Email comparison with tracked changes to reviewers
• Version Control: Archive comparison results for audit trail
• Contract Redlining: Distribute redlined contracts showing changes
• Document Approval: Send comparison to approvers for review

Scenario Examples

The PDF4me Compare Documents action in Zapier provides comprehensive scenario templates designed for real-world comparison needs:

Contract Redlining

Automated Contract Version Comparison Workflow

Compare contract versions and generate redline automatically:

Complete Scenario Steps:

1. Trigger: New contract version uploaded to Google Drive contracts folder
2. Get Original Contract: Retrieve baseline contract version from archive
3. Get Revised Contract: Retrieve new version from contracts folder
4. Compare Contracts: Set First Document = original, Second Document = revised
5. Track Content Only: Set Ignore Formatting = Yes to focus on content changes
6. Set Author: Author = "Legal Review" for tracking attribution
7. Ignore Fields: Set Ignore Fields = Yes (dates auto-update)
8. Generate Redline: Receive comparison document with tracked changes
9. Email Legal Team: Send redline to attorneys for review
10. Archive Comparison: Store redline in contract review archive

Business Benefits:

• Compares 50+ contract versions monthly automatically
• Tracked changes clearly show all modifications
• Ignore formatting focuses review on substantive changes
• Reduces manual comparison time from 30 minutes to 1 minute per contract

Create Zap

Policy Review

Automated Policy Document Comparison Workflow

Compare policy versions showing all changes for review:

Complete Scenario Steps:

1. Trigger: Policy document revision submitted for review
2. Get Current Policy: Retrieve approved current policy from SharePoint
3. Get Proposed Revision: Retrieve revised policy from review folder
4. Compare Policies: Set First Document = current, Second Document = proposed
5. Track All Changes: Leave all ignore flags = No for comprehensive tracking
6. Set Author: Author = "Policy Review Committee"
7. Generate Comparison: Receive document with all tracked changes
8. Email Review Committee: Send comparison to committee members
9. Upload to Review Portal: Save comparison to committee review folder
10. Log Review: Record comparison event in policy review log

Business Benefits:

• Compares 20+ policy revisions monthly automatically
• Comprehensive change tracking shows all modifications
• Committee sees exactly what changed from current version
• Eliminates manual side-by-side comparison saving 45 minutes per policy

Create Zap

Document Audit

Automated Document Version Audit Workflow

Compare document versions for compliance audit trail:

Complete Scenario Steps:

1. Trigger: Quarterly compliance audit document review scheduled
2. List Document Versions: Get all versions from version control folder
3. Iterate Version Pairs: Loop through consecutive version pairs
4. Compare Each Pair: Compare V1 vs V2, V2 vs V3, etc.
5. Set Audit Author: Author = "Compliance Audit" for tracking
6. Ignore Auto-Fields: Set Ignore Fields = Yes (prevent false changes)
7. Generate Comparison: Receive tracked changes for each comparison
8. Store Comparisons: Save all comparison files to audit folder
9. Generate Report: Create summary report of changes across versions
10. Email Compliance: Send audit report to compliance officer

Business Benefits:

• Audits 100+ document version pairs quarterly automatically
• Complete audit trail shows evolution of controlled documents
• Tracked changes provide visual evidence of modifications
• Reduces manual audit time from 40 hours to 4 hours per quarter

Create Zap

Industry Use Cases & Applications

Legal & Professional

• 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

Compliance & Regulatory

• Policy Version Control: Compare policy revisions tracking all regulatory compliance changes
• Procedure Updates: Compare SOP versions documenting process improvement modifications
• Regulatory Filing Review: Compare draft vs final regulatory submissions identifying changes
• Audit Document Tracking: Compare audit file versions for compliance audit trail documentation
• Controlled Document Management: Track changes in quality management system controlled documents

Corporate & Business

• Proposal Review: Compare RFP response drafts tracking team edits and improvements
• Report Revisions: Compare financial report versions showing analyst corrections
• Strategic Plan Updates: Compare planning document versions tracking strategic changes
• Board Package Review: Compare board materials versions identifying updates before distribution
• Vendor Agreement Negotiation: Track vendor contract changes throughout negotiation process

Publishing & Documentation

• Manuscript Editing: Compare manuscript versions tracking author and editor changes
• Technical Documentation: Compare technical doc revisions showing engineering updates
• User Manual Updates: Track changes in user documentation across product versions
• Translation Review: Compare translated documents vs originals tracking translation modifications
• Style Guide Enforcement: Compare documents vs style guide templates identifying deviations

Get Help

Zapier IntegrationGet your API KeyZapier Documentation