Element Exists
Check for the existence of web elements before proceeding
Inputs
☐ Description (Optional)
A brief note explaining what this check is for. This is not an AI prompt.
Good Example: “Check if login button exists before clicking”
Bad Example: “Look for something on the page”
Why it’s bad? Too vague, doesn’t specify what element to look for
☐ Element Type (Required)
Choose how to identify the element:
CSS Selector
Use standard CSS selectors (e.g., .button, #login-form)
XPath
Use XPath expressions (e.g., //button[text()='Submit'])
☐ Retry Settings (Required)
Try For
Number of retries before failure (Default: 3)
Timeout
Milliseconds to wait between retries (Default: 500ms)
☐ Error Handling (Optional)
Choose whether to throw an error if element isn’t found:
- Disabled (Default): Continue automation
- Enabled: Stop execution with error
Outputs
✓ Element Found Path
If the element is found within the specified retry attempts:
- Automation continues down this path
- Use for actions that require the element’s presence
- Example: Click the login button after confirming it exists
✗ Element Not Found Path
If the element is not found after all retry attempts:
- With Error Handling Disabled: Automation continues down this path
- With Error Handling Enabled: Automation stops with error
- Use for alternative flows or fallback actions
- Example: Show “Try Later” message if product is out of stock
Configure both paths to handle all scenarios gracefully. The Element Not Found path is especially useful for implementing fallback behaviors or alternative workflows.
Usage Examples
1. Login Button Check
#login-button2. Product Price Verification
//span[@class=‘product-price’]3. CAPTCHA Detection
#captcha-boxNotes
- Use descriptive selectors to uniquely identify elements
- Adjust retry settings based on page load times
- Enable error handling for critical elements