What is the Word2Text node used for in n8n workflows?
The Word2Text node is designed to extract the plain textual content from Microsoft Word documents (DOCX/DOC files). It acts as a processing step, transforming complex file data into simple text for further workflow processing or analysis, often following a file download Integration.
How does the Word2Text node handle file input?
This node typically receives binary document data from a preceding node, such as an HTTP Request or a cloud storage Integration. It then processes the file content and outputs the extracted text, which can then be passed to subsequent nodes.
Does the Word2Text node preserve formatting or images from the Word document?
No, its primary function is strictly text extraction. It strips all complex formatting, images, and embedded objects, providing only the raw, readable text, making the data lighter for later processing by other nodes.
Can Word2Text act as a trigger for a workflow?
No. Word2Text is a utility node, meaning it must be placed within a running workflow. It requires a preceding node or a dedicated trigger node (like a Webhook or a cloud storage listener) to initiate the process and provide the input file.
What are common Integrations used before the Word2Text node?
Common Integrations include file storage services (like Google Drive, Dropbox, or S3) or email services. These services use their specific nodes to download the Word file, which then feeds the binary data into the Word2Text node for processing.