Runs onWrit CloudDesktopSelf-hosted
On this page
Hover
The hover step moves the pointer over an element without clicking, which is useful for menus, tooltips, and controls that only appear on hover.
In a workflow, this is a step object with "type": "hover". 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 | The element to hover over. |
Example
A single hover step as it appears in a workflow's steps array:
{
"type": "hover",
"config": { "selector": "nav .account-menu" }
}How it behaves
- Often used right before a click on a dropdown item that is hidden until hover.
- Pair with a short wait if the revealed menu animates in.
Where it runs
The hover 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.