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, Get Tracking Changes In Word, extracts the tracked changes from a Microsoft Word document. It is useful when you want to programmatically analyze or review edits made in a Word file, such as insertions, deletions, and formatting changes that are recorded via Word's "Track Changes" feature.

Common scenarios include:

Automating document review workflows by extracting change logs.
Integrating with document management systems to track revisions.
Generating reports on document edits for auditing purposes.

For example, you can provide a Word document (via binary data, base64 string, or URL) and receive a JSON output detailing all tracked changes, which can then be used for further processing or visualization.

Properties

Name	Meaning
Input Data Type	How the Word document is provided. Options: • Binary Data (from previous node) • Base64 String • URL
Binary Property	Name of the binary property containing the Word document (used if Input Data Type is Binary Data).
Document Name	Name of the Word document including extension (used if Input Data Type is Binary Data).
Base64 Document Content	Base64 encoded content of the Word document (required if Input Data Type is Base64 String).
Document Name (required)	Name of the Word document including extension (required if Input Data Type is Base64 String or URL).
Document URL	URL pointing to the Word document (required if Input Data Type is URL).
Output File Name	Name for the output JSON file containing the tracking changes (default: `tracking_changes.json`).

Output

The node outputs a JSON object representing the tracked changes extracted from the Word document. This JSON typically includes details about each change such as type (insertion, deletion, etc.), author, timestamp, and affected text segments.

If configured, the output can also be saved as a JSON file named according to the "Output File Name" property.

The node does not output binary data directly; its main output is structured JSON describing the tracked changes.

Dependencies

Requires access to the Word document either as binary data, base64 string, or accessible via URL.
Likely depends on an external service or API capable of parsing Word documents and extracting tracked changes.
Requires appropriate API authentication credentials configured in n8n to interact with the external service.
Network access is needed if providing the document via URL.

Troubleshooting

Common Issues:
- Providing an incorrect or inaccessible URL will cause failures in fetching the document.
- Supplying invalid base64 content or corrupted binary data may result in parsing errors.
- Missing required properties depending on the input data type (e.g., missing document name when using base64 or URL).
- API authentication errors if credentials are not set up correctly.
Error Messages:
- Errors related to document retrieval (e.g., "Failed to fetch document") indicate issues with URL or network.
- Parsing errors like "Invalid Word document format" suggest corrupted or unsupported files.
- Authentication errors will mention authorization failure; ensure API keys or tokens are valid and configured.
Resolutions:
- Verify URLs are correct and publicly accessible or accessible within your network.
- Confirm base64 strings are properly encoded and represent valid Word documents.
- Ensure all required fields are filled based on the selected input data type.
- Check and update API credentials in n8n settings.

Links and References

Note: The above summary is based on static analysis of the node's code and provided property definitions without runtime execution.