Runs onWrit CloudDesktopSelf-hosted
On this page
Click
The click step clicks a single element. The recorder captures a stable selector plus the element description and coordinates, so replay can re-find the element even when the page shifts slightly.
In a workflow, this is a step object with "type": "click". Steps run in order, and each step can read the outputs of the steps before it. See the full workflows reference for the 30+ step types.
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Fields
| Field | Type | Description |
|---|---|---|
selector required | selector | CSS or text selector for the target element. |
description | string | The recorded human-readable label of the element, used to re-find it if the selector goes stale. |
coordinates | object | Recorded {x, y} position, kept as a last-resort fallback. |
Example
A single click step as it appears in a workflow's steps array:
{
"type": "click",
"config": { "selector": "button:has-text('Add to cart')" }
}How it behaves
- The element is scrolled into view and awaited before the click fires.
- When a click opens a new tab, follow it with wait_for_tab.
Where it runs
The click step executes wherever the run executes. On your local or BYO agent there is no compute charge and the agent can reach intranet-only systems; on Writ cloud the run is metered by running time (~$0.12 per browser-hour, from your plan’s included usage wallet.
What next
- Workflows - the full step vocabulary and the workflow object.
- Recorder - capture steps by clicking through a site.
- Managed endpoints - turn the workflow into a REST endpoint, or an MCP tool.