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 enables the "Track Changes" feature in a Microsoft Word document. When enabled, any edits made to the document will be tracked, allowing users to see additions, deletions, and formatting changes. This is particularly useful in collaborative editing scenarios where multiple reviewers need to provide feedback or suggest modifications while preserving the original content.

Practical examples include:

Legal teams reviewing contract drafts with visible change tracking.
Editors collaborating on manuscripts or reports.
Project teams sharing documents that require approval with clear visibility of all modifications.

Properties

Name	Meaning
Input Data Type	How the Word document is provided for processing. Options: Binary Data (from previous node), Base64 String (encoded content), URL (link to the document).
Input Binary Field	The name of the binary property containing the Word document when using Binary Data input type (usually "data").
Base64 Word Content	The base64 encoded string representing the Word document content, used if Input Data Type is Base64 String.
Word Document URL	The URL pointing to the Word document to process, used if Input Data Type is URL.
Output File Name	The desired file name for the output Word document with tracking enabled. Defaults to "tracking_enabled_output.docx".
Async	Whether to process the operation asynchronously. Defaults to true.

Output

The node outputs the processed Word document with "Track Changes" enabled. The output includes:

A JSON object containing metadata about the processed file.
A binary data field containing the modified Word document file content, ready for further use or download.

If the input was binary or base64, the output will similarly contain the processed document in binary form under the specified binary property.

Dependencies

Requires access to an external document processing service capable of enabling track changes in Word documents.
Needs appropriate API credentials or authentication tokens configured in n8n to interact with this service.
Internet access may be required if the input document is provided via URL.

Troubleshooting

Common Issues:
- Invalid or inaccessible URL when providing the document via URL input type.
- Incorrect binary property name leading to missing input document.
- Malformed base64 string causing decoding errors.
- Missing or invalid API credentials resulting in authorization failures.
Error Messages:
- "Input document not found": Check that the binary property name matches the actual input data.
- "Failed to fetch document from URL": Verify the URL is correct and accessible.
- "Invalid base64 content": Ensure the base64 string is properly encoded without extra characters.
- "Authentication failed": Confirm API credentials are correctly set up in n8n.

Resolving these typically involves verifying input parameters, ensuring proper credential configuration, and confirming network accessibility.