Runs onWrit CloudDesktopSelf-hosted
On this page
Select
The select step picks an option in a native <select> element. For custom dropdowns rendered as menus, record a click on the option instead.
In a workflow, this is a step object with "type": "select". 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 <select> element. |
value required | string | The option to select (placeholders supported). |
Example
A single select step as it appears in a workflow's steps array:
{
"type": "select",
"config": { "selector": "select[name='country']", "value": "United States" }
}How it behaves
- Custom (non-native) dropdowns are a click on the trigger plus a click on the option.
- The value can come from the declared inputs, so one workflow serves many choices.
Where it runs
The select 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.