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 in scenarios where you need to programmatically review or process edits made in a Word document, such as for document auditing, version control, or automated reporting of modifications.

Practical examples include:

Automatically extracting and summarizing all revisions made by collaborators in a shared Word document.
Integrating with document management systems to track changes history.
Generating reports on document edits without manually opening the file.

Properties

Name	Meaning
Input Data Type	How the Word document is provided. Options: - Binary Data (from previous node) - Base64 String (encoded content) - URL (link to the document)
Binary Property	The name of the binary property containing the Word document (used when Input Data Type is Binary Data). Default is "data".
Document Name	The name of the Word document including its extension (e.g., `document.docx`). Required when Input Data Type is Base64 or URL; optional for Binary Data.
Base64 Document Content	The base64 encoded content of the Word document. Required if Input Data Type is Base64 String.
Document URL	The URL pointing to the Word document. Required if Input Data Type is URL.

Output

The output JSON contains the extracted tracking changes data from the Word document. This typically includes details about insertions, deletions, formatting changes, and comments that were tracked in the document.

If the input was binary or base64, the node processes the document content directly. If a URL was provided, it fetches the document from the given link before extraction.

The node does not output binary data itself but returns structured JSON representing the tracked changes.

Dependencies

Requires access to the Word document either as binary data, base64 string, or via a URL.
May require an API key credential or authentication token configured in n8n to interact with the external service performing the extraction (implied by the bundled code referencing many actions).
Network access is needed if providing a URL to fetch the document.

Troubleshooting

Common issues:
- Providing an incorrect or inaccessible URL will cause failures fetching the document.
- Missing or incorrect binary property name when using binary input will result in no document found.
- Invalid base64 content or corrupted Word documents may cause parsing errors.
- Not specifying the document name when required can lead to errors.
Error messages:
- Errors related to document retrieval (e.g., network errors, 404 not found) indicate problems with the URL or connectivity.
- Parsing errors suggest the document is not a valid Word file or is corrupted.
- Validation errors occur if required parameters are missing.
Resolutions:
- Verify URLs are correct and accessible.
- Ensure binary property names match the actual input data.
- Confirm base64 strings are properly encoded.
- Always provide the document name when required.

Links and References

Note: This summary is based on static analysis of the node's source code and provided properties. Runtime behavior depends on the external service handling the Word document processing.