Description:

This step converts a Microsoft Word document into plain text format.

The Convert Word to Text workflow step reads a Microsoft Word document from the specified file path, extracts its textual content, generates a plain text (.txt) file, and stores the path of the generated text file in a FlowWright Variable or Global Variable.

This step provides an efficient way to prepare Word documents for text processing, indexing, searching, natural language processing (NLP), AI workflows, document archiving, or downstream business automation.

The generated text file can be consumed immediately by subsequent workflow steps without requiring Microsoft Word automation or custom document-processing code.

The step supports:

• Microsoft Word document processing
• Word to text conversion
• Automatic text file generation
• Storage of the generated text file path
• Integration with FlowWright Variables and Global Variables
• Text-based document processing workflows

This step can be used for:

• Document indexing
• Full-text search
• AI document analysis
• Content extraction
• Data migration
• Document archiving
• Business process automation

Usage:

The Convert Word to Text step is typically placed before document indexing, AI analysis, content extraction, search operations, reporting, or document migration activities.

The workflow opens the specified Word document, extracts its textual content, generates a plain text file, stores the generated file path, and makes the result available to subsequent workflow steps.

A typical workflow might look like this:

Once the text file has been generated, later workflow steps can:

• Analyze document content
• Index document text
• Perform keyword searches
• Generate summaries
• Feed text into AI models
• Archive extracted content
• Continue workflow execution

The Word document must already exist and be accessible before this step is executed.

Example:

Let’s build and execute the “WordToTextDef” example.          

• Create a new process definition called “WordToTextDef” and open it in Designer mode.
• Drag a “WordToText” step to the canvas. 
• Connect the “Start” step to the “wordToText” steps, as shown above. 
• Define a variable or a global to store the file path. 
• Click the "WordToText" step to configure its "Required" properties. Provide a name for the step. Provide the path to the Word document on the app server. Provide a variable or a global reference to store the output file path. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

• Save the Process Definition. Create a new Process Instance and execute it. When the workflow reaches the Convert Word to Text step, FlowWright opens the specified Microsoft Word document, extracts its text, generates a plain-text file, and stores the path to the generated file in the configured Variable or Global Variable. If the operation completes successfully, the workflow follows the True return path. If the Word document cannot be found, is corrupted, is in an unsupported format, or the text file cannot be created, the workflow follows the False return path. Click the process step to view its properties. The step should successfully generate the text file, populate the configured Variable or Global Variable with the generated file path, and return True upon completion.

Tips:

• Verify that the specified Word document exists before executing the workflow.
• Store the path to the generated text file in a Global Variable when multiple workflow steps require access to the extracted content.
• Use workflow variables to dynamically specify the path to the Word document.
• Combine this step with AI, OCR, or text analysis workflow steps to automate intelligent document processing.
• Use the generated text file for indexing, keyword searches, document classification, or content extraction.
• Archive the generated text file when maintaining searchable document repositories.
• Use the True and False return paths to implement appropriate success and exception handling.
• Combine this step with Get File Information, Azure OpenAI Chat Completion, PDF to HTML, JSON to XML, Send Email, or Archive Document workflow steps to automate complete document processing workflows.

Notes:

• The input file must be a supported Microsoft Word document.
• The FlowWright server must have permission to read the source document and create the output text file.
• The path to the generated text file is stored in the configured Variable or Global Variable.
• Invalid file paths, corrupted documents, unsupported document formats, or insufficient file system permissions may cause the step to return False.
• This step extracts only the text and does not preserve document formatting, images, tables, headers, or other Word-specific formatting features.
• The original Word document is not modified during the conversion process.
• The workflow should include appropriate handling for both True and False return paths.
• Converting Word documents to plain text is particularly useful for AI-assisted document analysis, search indexing, compliance scanning, content migration, and downstream text processing workflows.

Definition Sample:

You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition page.

Note: Verify and complete any missing configuration after importing the sample, including:

• Word file path
• Text file path Variable or Global Variable mapping
• File system permissions
• Workflow variable definitions
• Environment-specific settings

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.