Description:

This step reads data from a web page using an HTML Element ID.

The Read Web Data Using Element ID workflow step retrieves the HTML content from a specified URL, searches the page for an HTML element with the specified Element ID, extracts its content, and stores the result in a FlowWright Variable or a Global Variable.

Unlike the Read Web Data Using XPath step, which allows complex XPath expressions, this step provides a simplified mechanism for retrieving content from web pages that expose unique HTML element identifiers.

This step provides an efficient way to automate web data extraction for dashboards, status pages, reporting, monitoring, integrations, validation workflows, and business process automation.

The extracted value can immediately be consumed by subsequent workflow steps.

The step supports:

• Reading web page content
• HTML Element ID lookup
• Dynamic URL configuration
• Storage of extracted data in Variables or Global Variables
• Integration with FlowWright workflow automation
• Automated web content retrieval

This step can be used for:

• Web data extraction
• Dashboard monitoring
• Status page monitoring
• Content retrieval
• Business intelligence
• System integrations
• Business process automation

Usage:

The Read Web Data Using Element ID step is typically placed before reporting, validation, notifications, integrations, or business rule processing activities that require information from a web page containing uniquely identified HTML elements.

The workflow retrieves the specified web page, locates the configured HTML element, stores the extracted value, and makes the result available to subsequent workflow steps.

A typical workflow might look like this:

Once the web data has been extracted, later workflow steps can:

• Compare retrieved values
• Generate reports
• Update workflow variables
• Trigger notifications
• Call REST APIs
• Execute business rules
• Continue workflow execution

The target website must be accessible before this step is executed.

Example:

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

• Create a new process definition named “clsWebReadDataDef” and open it in designer mode.
• Drag a “clsWebReadData” step onto the canvas. 
• Connect the dots between the “Start” step and the “clsWebReadData” step, as shown above. 
• Click the "clsWebReadData" step to configure its "Required" properties. Enter the URL from which to read the data. Enter the HTML element ID from which to read the data. Enter the variable or global reference to store the result. Click the Save button. Note: Click the "AI Predict" button to have 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 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 Read Web Data Using Element ID step, FlowWright retrieves the specified web page, searches for the configured HTML Element ID, extracts the associated content, and stores the result in the configured Variable or Global Variable. If the operation completes successfully, the workflow follows the True return path. If the website cannot be reached, the URL is invalid, the specified Element ID cannot be found, or the page cannot be processed, the workflow follows the False return path. Click the process step to view its properties. The step should successfully retrieve the requested web content, populate the configured Variable or Global Variable with the extracted value, and return True upon completion.

Tips:

• Verify that the specified URL is accessible from the FlowWright server.
• Inspect the web page to confirm that the required HTML element has a unique Element ID.
• Use workflow variables to dynamically specify the URL or Element ID during workflow execution.
• Use this step when retrieving content from a single known HTML element rather than performing more complex document searches.
• Store extracted values in Global Variables when multiple workflow steps require access to the retrieved information.
• Consider implementing retry logic for external websites that may be temporarily unavailable.
• Use the True and False return paths to implement appropriate success and exception handling.
• Combine this step with Read Web Data Using XPath, REST Call, Update Variables, Send Email, Conditional Routing, or Generate Report workflow steps to automate web monitoring and integration workflows.

Notes:

• The target website must be reachable from the FlowWright server.
• The specified HTML Element ID must exist within the retrieved web page.
• If multiple elements use the same ID, the result may be unpredictable.
• Invalid URLs, inaccessible websites, missing Element IDs, or page processing errors may cause the step to return False.
• The extracted value is stored in the configured Variable or Global Variable.
• This step retrieves web content only and does not modify the target website.
• The workflow should include appropriate handling for both True and False return paths.
• For complex HTML documents or scenarios requiring multiple values or hierarchical navigation, consider using the Read Web Data Using XPath step instead.

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:

• Target URL
• HTML Element ID
• Result Variable or Global Variable mapping
• Network connectivity
• Workflow variable definitions
• Environment-specific settings

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

Click here to download the sample file.