Description:

This step converts a PDF document into HTML format.

The PDF to HTML workflow step reads a PDF document from the specified file path, converts the document into an HTML representation while preserving its textual content and layout as closely as possible, and stores the path of the generated HTML file in a FlowWright Variable or Global Variable.

This step provides an efficient way to prepare PDF documents for web publishing, browser viewing, content extraction, document indexing, search operations, email rendering, or downstream workflow processing.

The generated HTML file can be consumed immediately by subsequent workflow steps without requiring manual conversion or third-party utilities.

The step supports:

• PDF to HTML conversion
• Automatic HTML file generation
• Storage of the generated HTML file path
• Integration with FlowWright Variables and Global Variables
• Browser-friendly document output
• Integration with document processing workflows

This step can be used for:

• Web publishing
• Document viewing
• Content extraction
• Search indexing
• Email generation
• Document migration
• Business process automation

Usage:

The PDF-to-HTML step is typically performed before document publishing, indexing, email generation, browser presentation, or content processing.

The workflow opens the specified PDF document, converts it into HTML format, stores the generated HTML file path, and makes the output available for subsequent workflow steps.

A typical workflow might look like this:

Once the HTML document has been generated, later workflow steps can:

• Display the document in a web browser
• Publish content to web portals
• Index document contents
• Send HTML emails
• Archive converted documents
• Process HTML content
• Continue workflow execution

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

Example:

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

• Create a new process definition named “PdfToHtmlDef” and open it in designer mode. 
• Drag a “PdfToHtml” step to the canvas. 
• Connect the dots between the “Start” step and the “PdfToHtml” step, as shown above. 
• Define a variable or a global to hold the HTML file path. 
• Click the "PdfToHtml" step to configure its "Required" properties. Provide a name for the step. Provide the path to the PDF input file on the app server. Provide a variable or global reference to store the path to the HTML output file. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• Click the "Email" step to configure its "Required" properties. Provide a name for the step, then click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• Click the "Email" step to configure its "Optional" properties. Set the email recipients. Enter the email subject and message content. Click the File Attachment button. Enter the variable or global reference that holds the HTML file path as shown below. Click the Save button. 

• 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 PDF to HTML step, FlowWright reads the specified PDF document, converts it into HTML format, creates the HTML output file, and stores the generated HTML file path in the configured Variable or Global Variable. If the operation completes successfully, the workflow follows the True return path. If the PDF file cannot be found, the document is invalid or corrupted, the conversion process fails, or the HTML output cannot be created, the workflow follows the False return path. Click the process step to view its properties. The step should successfully generate the HTML document, populate the configured Variable or Global Variable with the path to the generated HTML file, and return True upon completion.

• The email containing the HTML file attachment is shown here for reference. 

Tips:

• Verify that the PDF document exists before executing the workflow.
• Store the generated HTML file path in a Global Variable if multiple workflow steps require access to the converted document.
• Use workflow variables to dynamically specify the input PDF file.
• Validate the generated HTML before publishing it to external systems.
• Combine this step with document download, indexing, or publishing steps to automate document conversion workflows.
• Use the stored HTML file path when sending HTML content or publishing documents to web applications.
• Use the True and False return paths to implement appropriate success and exception handling.
• Combine this step with Remove Blank Pages, PDF Validate Signature, Get File Information, Send Email, Archive Document, or REST Call workflow steps to automate complete PDF processing workflows.

Notes:

• The input file must be a valid PDF document.
• The FlowWright server must have permission to read the PDF file and create the HTML output file.
• The generated HTML file path is stored in the configured Variable or Global Variable.
• Invalid file paths, corrupted PDF documents, or insufficient file system permissions may cause the step to return False.
• This step converts the document format without modifying the original PDF file.
• The appearance of the generated HTML depends on the structure and formatting of the source PDF.
• The workflow should include appropriate handling for both True and False return paths.
• PDF-to-HTML conversion is particularly useful for browser-based document viewing, content indexing, accessibility, and integration with web-based applications.

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:

• PDF file path
• HTML output 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.