Enable Tracking Changes in Word in n8n

What this node does

PDF4me - Enable Tracking Changes In Word activates the revision tracking flag in any DOCX file inside your n8n workflow. Once tracking is on, every insertion, deletion, and formatting change a reviewer makes is recorded with their name and a timestamp - ready for accept/reject review. Supply the document as binary data from a prior node, a Base64 string, or a public URL. The track-changes-ready DOCX is returned immediately for routing to email, SharePoint, Google Drive, or a downstream review workflow.

Authenticating Your API Request

Every PDF4me node in n8n requires valid Credentials. Create or select credentials that hold your PDF4me API key so the node can authenticate document processing requests securely.

Get your API Key

Important Facts You Should Not Miss

Only DOCX is supported - not DOC or RTF

The node processes the modern Open XML Word format (.docx). If your source document is in the older .doc binary format or RTF, convert it to DOCX first using the Convert Word to PDF Form or another conversion step before passing it here.

Safe to run on documents that already have tracking enabled

If the document already has change tracking active, the node returns it unchanged with a success status. This means you can place Enable Tracking Changes as a precautionary first step in any review pipeline without risking double-processing or errors on already-tracked documents.

Pair with Get Tracking Changes to read revisions programmatically

After reviewers have edited the document, the Get Tracking Changes In Word node extracts every recorded revision as structured JSON - reviewer name, change type, original text, and revised text. This lets you build full approval pipelines where changes are logged, compared, or routed for sign-off without opening the file manually.

Set Input Data Type, map the DOCX from the prior node, enter Output File Name with .docx extension, and run the workflow.

Parameters

Required: Input Data Type, the document field matching that type (Input Binary Field, Base64 Document Content, or File URL), Output File Name, and Binary Data Output Name. Async and Custom Profiles are optional.

Parameter	Required	What it does	Example
Input Data Type	Yes	Format of the source DOCX. Choose Binary Data to map from a prior node, Base64 String to supply encoded document data, or URL for a publicly accessible Word file.	Binary Data
Input Binary Field	Yes (Binary Data)	Property name of the binary DOCX from the prior node. Must match the binary output key of the upstream node.	data
Base64 Document Content	Yes (Base64)	Base64-encoded string of the DOCX to process. PDF4me decodes and activates tracking on the document.	UEsDBBQABgAI...
File URL	Yes (URL)	Publicly accessible URL to the source DOCX. PDF4me downloads and activates tracking on the document from this address.	https://example.com/contract.docx
Output File Name	Yes	Filename for the returned DOCX with tracking enabled, including .docx extension.	review_ready_contract.docx
Binary Data Output Name	Yes	Key name under which the output DOCX binary is stored in the n8n item. Downstream nodes reference this document by this name.	data
Async	No	When true, the operation runs asynchronously for large documents and returns immediately. Use for batch processing pipelines with large files.	false
Custom Profiles	No	Advanced configuration JSON string for additional processing options such as outputDataFormat or preserveMetadata.	{"preserveMetadata": true}

Quick Setup

1. Add a PDF4me node to your n8n workflow and select Enable Tracking Changes In Word.
2. Choose or create Credentials with your PDF4me API key.
3. Set Input Data Type and map the DOCX from the matching source field.
4. Enter Output File Name with .docx extension.
5. Click Execute Node. The returned DOCX has track changes active - route it to email, storage, or a review step.

Workflow Examples

Workflow ExamplesCommon n8n workflow patterns using Enable Tracking Changes In Word.

Send contracts to reviewers with tracking pre-enabled

1. Airtable triggers when a contract record is moved to "Ready for Legal Review."
2. Google Drive downloads the draft contract DOCX.
3. Enable Tracking Changes In Word activates revision tracking on the document.
4. Gmail sends the track-changes-ready DOCX to the legal team. Every edit they make is recorded with their name and timestamp.

Automate policy document review pipelines

1. SharePoint Watch triggers when a new policy document is uploaded to the "Draft Policies" library.
2. Enable Tracking Changes In Word activates revision tracking as a precautionary first step.
3. The track-ready document is emailed to the department head for review.
4. When the reviewed file returns, Get Tracking Changes In Word extracts all revisions into a Google Sheet for the compliance log.

Batch-enable tracking on all template documents

1. A scheduled trigger runs weekly and lists all DOCX files in the "Templates" folder on Google Drive.
2. A Split In Batches node processes each template individually.
3. Enable Tracking Changes In Word ensures every template has revision tracking active.
4. Google Drive replaces each file with the tracking-enabled version. A Slack message reports how many templates were updated.

Frequently Asked Questions

What exactly happens inside the DOCX when this node runs?+

The node activates the Word revision tracking flag in the document's Open XML structure. Once enabled, any editor who opens the file in Microsoft Word, Google Docs, or LibreOffice will have their insertions highlighted in a color, deletions shown with strikethrough, and formatting changes marked - all attributed to the reviewer and timestamped. Nothing else in the document changes.

Does this work on documents already in track-changes mode?+

Yes. If the DOCX already has revision tracking enabled, the node detects this and returns the document unchanged with a success status. This makes it safe to add as the first step of any review pipeline without worrying about double-processing or corrupting a document that already has revisions recorded.

How do I read the changes reviewers made after sending the document?+

Use the Get Tracking Changes In Word node on the reviewed DOCX. It returns a structured JSON array of every revision - including the change type (insert, delete, format), the original and revised text, the reviewer name, and the timestamp. Map this output into a Google Sheet, database, or email summary for your approval workflow.

Can I disable tracking changes with a separate node?+

Yes. The Disable Tracking Changes In Word node does the reverse - it turns off revision recording so subsequent edits are not tracked. Use it after the review cycle is complete and all revisions have been accepted or rejected, to produce a clean final document.

My source files are in .doc format, not .docx. Can I still use this node?+

Not directly. The node requires the modern Open XML .docx format. If your source files are in the older binary .doc format, run them through a conversion step first - for example, use the Convert to PDF node followed by a PDF-to-Word conversion, or pre-process them in another workflow step to produce .docx before enabling tracking.

Related Nodes

Get Tracking Changes In Word

Extract all recorded revisions as structured JSON after reviewers have edited the document - the natural next step in a review pipeline.

Disable Tracking Changes In Word

Turn off revision recording to produce a clean final document once all changes have been reviewed and accepted.

Compare Word Documents

Generate a redline comparison between two DOCX versions when you need to surface differences between a draft and a final without manually tracking edits.

Get Help

n8n IntegrationGet your API Keyn8n Documentation