Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

Get Tracking Changes In Word using n8n action

PDF4me Get Tracking Changes In Word retrieves and analyzes tracked changes from Microsoft Word documents through n8n automation workflows. Process Word files via n8n triggers, binary data, base64 strings, or public URLs to automatically detect tracked changes, extract edit history, identify modifications (additions, deletions, formatting changes), retrieve author information, and generate structured change reports. This solution is ideal for document review workflows, change analysis, approval processes, editorial tracking, compliance auditing, and collaborative editing analysis that require accurate change detection with detailed reporting and seamless integration.

Setup​

Add the PDF4me "Get Tracking Changes In Word" node to your n8n workflow and configure the required parameters. For initial setup instructions, see our n8n Integration Guide.

Prerequisites:

  • PDF4me API credentials
  • n8n workflow access
Get Your API Key

Configuration:

  1. Add PDF4me node to workflow
  2. Select "Get Tracking Changes In Word" action
  3. Configure input parameters (see below)
Get Tracking Changes In Word

Parameters​

Complete list of parameters for the Get Tracking Changes In Word action. Configure these parameters to control tracking changes detection.

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

| Parameter | Type | Description | Example | |-----------|------|-------------|---------|| | Input Data Type*** | String | Word Input Format Selection
• Choose the format of your Word document input
• PDF4me supports multiple input types
• Options: Binary Data, Base64 String, or URL | Binary Data | | Binary Property | String | Binary Data Reference (Required if Binary Data)
• Specify the property name for accessing binary Word document data
• Should match the binary data property name in your workflow
• Required when Input Data Type is "Binary Data" | data | | Base64 Document Content | String | Base64 Encoded Word Input (Required if Base64 String)
• Provide Word document data as base64 encoded string
• PDF4me automatically decodes and processes the document content
• Required when Input Data Type is "Base64 String" | UEsDBBQABgAI... | | File URL | String | Public Word URL Input (Required if URL)
• Provide a public/open permission URL to the Word document
• PDF4me downloads and processes the file for tracking changes analysis
• Required when Input Data Type is "URL" | https://abc.com/sample.docx | | Document Name*** | String | Input Document Filename
• Specify the name of the Word document being processed
• Helps with file identification and processing order
• Used in change detection operation | document.docx |

Advanced Options​

The following parameters are available in the Advanced Options section and are optional:

ParameterTypeDescriptionExample
Custom ProfilesStringNoPDF4me custom configuration profiles - Set additional options for the PDF4me Get Tracking Changes In Word operation using custom profiles. A custom profile is a string in JSON-like format containing predefined parameters for advanced change detection settings. Supports options like outputDataFormat, preserveMetadata, optimizeForPrinting, compressionLevel, and colorSpaceOptimization

Output​

Output Parameters​

ParameterTypeDescriptionExample
successBooleanPDF4me change detection operation status indicator - Boolean flag indicating the success or failure of the Word tracking changes detection process. PDF4me returns true for successful operations and false for any errors, enabling robust error handling in automated workflowstrue
messageStringPDF4me change detection operation status message - Human-readable status message providing details about the change detection process result. Includes success confirmation or error details for troubleshootingTracking changes retrieved successfully
fileNameStringPDF4me processed document filename - The complete filename of the processed Word document with proper .docx extension. PDF4me ensures unique naming and validates file format compliance for seamless integration with downstream processesdocument_with_changes.docx
mimeTypeStringPDF4me output MIME type - MIME type of the processed Word document, always "application/vnd.openxmlformats-officedocument.wordprocessingml.document" for .docx files. Useful for content type validation and proper file handling in web applicationsapplication/vnd.openxmlformats-officedocument.wordprocessingml.document
fileSizeNumberPDF4me processed document file size in bytes - The exact size of the processed Word document in bytes, provided by PDF4me for storage planning, bandwidth optimization, and file transfer monitoring. Essential for enterprise document management and workflow automation125430
docNameStringPDF4me document name reference - The name of the processed document for reference and tracking purposes. This matches the fileName for consistency in document management workflowsdocument_with_changes.docx
trackingChangesDetectedBooleanPDF4me tracking changes detection confirmation - Boolean flag confirming that tracking changes were successfully detected in the Word document. Useful for verifying that the change detection was applied correctlytrue
changesCountNumberPDF4me detected changes count - The number of tracked changes that were successfully detected in the Word document. Useful for tracking change detection effectiveness and document analysis results5

N8N Action Response​

The PDF4me Get Tracking Changes In Word API returns a response that can be viewed in multiple formats. Choose the view that best fits your needs:

JSON Response Format

The raw JSON response from the API:

[
  {
    "success": true,
    "message": "Tracking changes retrieved successfully",
    "fileName": "document_with_changes.docx",
    "mimeType": "application/vnd.openxmlformats-officedocument.wordprocessingml.document",
    "fileSize": 125430,
    "docName": "document_with_changes.docx",
    "trackingChangesDetected": true,
    "changesCount": 5
  }
]

Use Cases​

Document Review and Compliance Analysis​

  • Analyze legal contracts and policy documents to detect all tracked changes and modifications for compliance verification and audit trail maintenance
  • Process regulatory submissions and official documents by identifying tracked changes to ensure all modifications are properly documented and approved
  • Automate the review of collaborative documents to identify unauthorized changes and maintain document integrity in sensitive business processes

Collaborative Editing Workflow Management​

  • Monitor team collaboration by detecting and counting tracked changes in shared Word documents to understand editing activity and progress
  • Process training materials and educational content by analyzing tracked changes to provide feedback on writing improvements and content updates
  • Automate the analysis of document revisions to track the evolution of content and ensure quality control in content management workflows

Quality Assurance and Change Tracking​

  • Implement automated quality checks by detecting tracked changes in critical business documents to ensure all modifications are intentional and approved
  • Process technical documentation and user manuals by analyzing tracked changes to maintain version control and document accuracy
  • Automate the monitoring of document modifications in compliance-heavy industries to ensure all changes are properly tracked and documented

Get Help​

n8n Integration Guiden8n SampleGetting Started