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 "Disable Tracking Changes In Word" processes a Microsoft Word document to disable the "Track Changes" feature. When enabled, Track Changes records all edits made to a document, which can be distracting or undesirable in finalized documents. This operation removes or disables that tracking, resulting in a clean document without visible change marks.
Common scenarios where this node is beneficial include:
- Finalizing legal or business documents before sharing or archiving.
- Preparing documents for printing or distribution without markup clutter.
- Automating document workflows where tracked changes need to be cleared programmatically.
Practical example: You receive Word documents with multiple collaborators' edits tracked. Before sending the final version to clients, you use this node to disable tracking changes and produce a clean copy automatically.
Properties
| Name | Meaning |
|---|---|
| Input Data Type | Choose how to provide the Word document to process. Options: • Binary Data (from previous node) • Base64 String (base64 encoded content) • URL (link to the Word document) |
| Input Binary Field | Name of the binary property containing the Word document (usually "data"). Required if Input Data Type is Binary Data. |
| Base64 Word Content | Base64 encoded content of the Word document. Required if Input Data Type is Base64 String. |
| Word Document URL | URL pointing to the Word document to process. Required if Input Data Type is URL. |
| Output File Name | Desired filename for the output Word document after disabling tracking changes. Defaults to "tracking_disabled_output.docx". |
| Async | Boolean flag to process the operation asynchronously. Defaults to true. |
| Binary Data Output Name | Custom name for the binary data field in the node's output. Defaults to "data". |
Output
The node outputs the processed Word document as binary data under the specified binary data output name (default "data"). The binary data represents the Word file with tracking changes disabled.
The JSON output contains no additional fields beyond the input metadata unless an error occurs.
Dependencies
- Requires access to the Word document either as binary data, base64 string, or via a URL.
- No explicit external API keys or credentials are indicated by the static code.
- The node internally uses a bundled action module dedicated to disabling tracking changes in Word documents.
Troubleshooting
Common issues:
- Providing an invalid or corrupted Word document will cause processing errors.
- Incorrectly specifying the binary property name when using binary input type may result in missing input data.
- If using a URL, network issues or inaccessible URLs will cause failures.
Error messages:
- Errors related to file reading or parsing usually indicate invalid input format.
- Network errors when fetching from URL suggest connectivity or permission problems.
Resolutions:
- Verify the input document is a valid Word (.docx) file.
- Confirm the binary property name matches the actual input data.
- Ensure URLs are accessible and publicly reachable or authenticated properly outside this node.