Runs onWrit CloudDesktopSelf-hosted
On this page
End point
The end_point step marks where the workflow is considered complete. By default it completes immediately; with a condition it first waits for the page to prove the outcome — an element visible, expected text, or a URL pattern.
In a workflow, this is a step object with "type": "end_point". 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 |
|---|---|---|
condition_type | string | immediate (default), url_contains, url_equals, element_visible, element_exists, or text_visible. |
selector | selector | The element to wait for, with element_visible or element_exists. |
text | string | The text the page must show, with text_visible. |
url | string | The URL the page must reach, with url_contains or url_equals. |
timeout_ms | number | How long to wait for the condition before the run fails. Defaults to 30000. |
Example
A single end_point step as it appears in a workflow's steps array:
{
"type": "end_point",
"config": { "condition_type": "element_visible", "selector": ".order-confirmation" }
}How it behaves
- A conditioned end_point turns silent breakage into an honest failure: the run only succeeds when the page proves it.
- Place it last, after the steps that produce the outcome.
Where it runs
The end_point 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.