Skip to main content
Node type: click_element · Version: 1 · Category: Browser Click a recorded element. This node is not marked with the catalogue’s generic side-effect flag. That classification is not a guarantee that every configured operation is read-only; review the concrete action and its destination.

​
When to use this node

  • Activate a recorded button, link, menu item, or other interactive target.
  • Use double, right, or modified clicks when the application requires them.

​
Example: Open the reports view

Record the Open reports button, use a normal left click, and allow a short transition delay.
Example settings
This shows the important settings, not a complete exported node. The locator is shortened for readability; use the recorder to create the complete structured locator bundle.
  1. Record the target in a representative page state.
  2. Test the locator and confirm it matches exactly one element.
  3. Follow with Wait For or Navigate readiness when the click starts asynchronous work.

​
Configuration

​
Workflow JSON

The editor stores this node with the following implemented default configuration:
Default node configuration
Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

​
Inputs

This node has no typed ports in this direction.

​
Outputs

​
Execution behavior

  • sndbox tries the recorded accessible locator and retained fallbacks, recording every attempt in browser diagnostics.
  • waitAfterMs is a fixed post-click pause, not a proof that the expected result occurred.
  • The editor catalogue declares result (any) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

​
Common issues

  • If zero or several elements match, rerecord with a stable accessible name or test ID.
  • Avoid weak text or positional CSS selectors when the page offers a role, label, or stable test ID.

​
Where it can run

  • Desktop local runner
  • Paired self-hosted runner
  • Managed browser worker

​
Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.