Click Element

When to use

Reach for Click Element whenever a step in your automation needs to activate something on a web page the way a person would: pressing a button, following a link, opening a menu, or toggling a control.

• Click a Login or Submit button
• Open a navigation menu or dropdown trigger
• Select a menu item or tab
• Activate a checkbox or radio button

When not to use

• To read a value from the page, use Get Text instead.
• To set a form field's value directly, prefer Type Into or Set Value — clicking is for interactive controls, not text entry.
• To wait for something to appear before acting, pair this with Wait For Element rather than relying on the built-in timeout alone.

Best practices

• Prefer stable selectors (an id, a data-* attribute, or an ARIA role) over brittle, index-based CSS paths that break when the page changes.
• Increase Timeout for slow-loading or heavily dynamic applications.
• Keep Wait for Element on so the click retries until the element is actually present and interactable.

Common mistakes

• Wrong selector — the element exists but the selector matches nothing, or matches a hidden duplicate. Verify the selector against the live page.
• Element inside an iframe — switch to the frame first; a top-level selector will not find it.
• Clicking too early — the element is not yet rendered. Add a Wait For Element step or raise the timeout.

FAQs

Can it click hidden elements? It clicks elements the browser considers interactable. Truly hidden elements (display:none) cannot be clicked — reveal them first.

Does it support iframes? Yes, once you have switched into the frame that contains the element.

Can I use a dynamic selector? Yes — bind the selector to a variable or expression to target elements whose attributes change between runs.