Actions80
- Add Attachment To PDF
- Add Barcode To PDF
- Add Form Fields To PDF
- Add HTML Header Footer
- Add Image Stamp To PDF
- Add Image Watermark To Image
- Add Margin To PDF
- Add Page Number To PDF
- Add Text Stamp To PDF
- Add Text Watermark To Image
- AI-Invoice Parser
- AI-Process Contract
- AI-Process HealthCard
- Classify Document
- Compress Image
- Compress PDF
- Convert HTML To PDF
- Convert Image Format
- Convert JSON To Excel
- Convert Markdown To PDF
- Convert PDF To Editable PDF Using OCR
- Convert PDF To Excel
- Convert PDF To PowerPoint
- Convert PDF To Word
- Convert To PDF
- Convert URL to PDF
- Convert VISIO
- Convert Word to PDF Form
- Create Images From PDF
- Create PDF/A
- Create Swiss QR Bill
- Crop Image
- Delete Blank Pages From PDF
- Delete Unwanted Pages From PDF
- Split PDF By Barcode
- Disable Tracking Changes In Word
- Enable Tracking Changes In Word
- Extract Attachment From PDF
- Extract Form Data From PDF
- Extract Pages From PDF
- Extract Resources
- Extract Table From PDF
- Extract Text By Expression
- Extract Text From Word
- Fill PDF Form
- Find And Replace Text
- Flip Image
- Flatten PDF
- Generate Barcode
- Generate Document Single
- Generate Documents Multiple
- Get Document From Pdf4me
- Get Image Metadata
- Get PDF Metadata
- Split PDF By Swiss QR
- Get Tracking Changes In Word
- Image Extract Text
- Linearize PDF
- Merge Multiple PDFs
- Overlay PDFs
- Parse Document
- Protect PDF
- Read Barcode From Image
- Read Barcode From PDF
- Read SwissQR Code
- Remove EXIF Tags From Image
- Repair PDF Document
- Replace Text With Image
- Replace Text With Image In Word
- Resize Image
- Rotate Document
- Rotate Image
- Rotate Image By EXIF Data
- Rotate PDF Page
- Sign PDF
- Split PDF By Text
- Split PDF Regular
- Unlock PDF
- Update Hyperlinks Annotation
- Upload File To PDF4me
Overview
This node operation enables the "Track Changes" feature in a Microsoft Word document. It processes an input Word document and outputs a new version with change tracking activated, which is useful for collaborative editing and reviewing. This functionality benefits scenarios where multiple users need to review or edit a document while keeping track of all modifications, such as legal contracts, editorial workflows, or team reports.
Practical examples:
- Automatically enable change tracking on contract drafts before sending them out for review.
- Prepare documents for collaborative editing by activating tracking changes to monitor all edits.
- Convert received Word files into versions that highlight all future modifications for audit purposes.
Properties
| Name | Meaning |
|---|---|
| Input Data Type | Choose how to provide the Word document to process. Options: Binary Data (from previous node), Base64 String, or URL. |
| Input Binary Field | Name of the binary property containing the Word document when using Binary Data input type (usually "data"). |
| Base64 Word Content | Base64 encoded string representing the Word document content (used if Input Data Type is Base64). |
| Word Document URL | URL pointing to the Word document to process (used if Input Data Type is URL). |
| Output File Name | Desired file name for the output Word document with tracking enabled. |
| Async | Whether to process the operation asynchronously (true/false). |
| Binary Data Output Name | Custom name for the binary data field in the node's output (default is "data"). |
Output
The node outputs the processed Word document with tracking changes enabled as binary data. The output includes:
- A JSON object per input item.
- A binary property containing the Word document file data, named according to the "Binary Data Output Name" property (default "data").
- The binary data represents the Word document (.docx) with change tracking activated, ready for download or further processing.
Dependencies
- Requires access to the input Word document either as binary data, base64 string, or via a URL.
- No explicit external API keys or services are indicated in the provided code snippet.
- The node relies on internal action implementations to perform the enabling of tracking changes in Word documents.
Troubleshooting
Common issues:
- Providing an invalid or inaccessible URL may cause failures in fetching the document.
- Incorrect base64 encoding or corrupted binary data will result in processing errors.
- Output file name conflicts or invalid characters might cause issues when saving the output.
Error messages:
- Errors related to file reading or parsing typically indicate problems with the input document format or content.
- Network errors when using URL input suggest connectivity or permission issues.
Resolutions:
- Verify the input document source and ensure it is accessible and correctly formatted.
- Confirm base64 strings are properly encoded without extra whitespace or corruption.
- Use valid file names and avoid special characters unsupported by file systems.