PDF4me

Comprehensive PDF and document processing: generate barcodes, convert files, extract data, manipulate images, and automate workflows with the PDF4ME API

Actions80

Overview

This node operation "Disable Tracking Changes In Word" processes a Microsoft Word document to disable the "Track Changes" feature. This is useful when you want to finalize a document by accepting all tracked changes and removing the markup, making the document clean for sharing or archiving.

Common scenarios include:

Finalizing edited documents before distribution.
Preparing documents for legal or official use where change tracking should be removed.
Automating document workflows that require clean versions without revision marks.

Practical example:

You receive a Word document with multiple tracked changes from collaborators. Using this node, you can automatically disable tracking changes and output a clean version of the document ready for publishing.

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 Word document content. Required if Input Data Type is Base64 String.
Word Document URL	URL to the Word document to process. Required if Input Data Type is URL.
Output File Name	Name for the output processed Word document file. Defaults to "tracking_disabled_output.docx".
Async	Boolean flag to process asynchronously. Defaults to true.

Output

The node outputs the processed Word document with tracking changes disabled. The output includes:

A JSON object containing metadata about the processed file.
A binary data field containing the Word document file content with tracking changes turned off.

If the input was binary or base64, the output will be a binary file named as specified in "Output File Name".

Dependencies

Requires access to the Word document either as binary data, base64 string, or via a URL.
No explicit external API keys or services are indicated in the code snippet; processing appears to be handled internally or via bundled dependencies.
Ensure the node has proper permissions to fetch files from URLs if using the URL input option.

Troubleshooting

File not found or inaccessible URL: If providing a URL, ensure the link is publicly accessible or accessible from the n8n environment.
Invalid Word document format: Input must be a valid .docx Word document; corrupted or unsupported formats may cause errors.
Incorrect binary property name: When using binary data input, verify the binary property name matches the actual input data property.
Async processing issues: If asynchronous processing is enabled but results are delayed or missing, try disabling async to troubleshoot.
Error messages related to file processing: These usually indicate invalid input data or internal processing failures; check input data integrity and format.