Runs onWrit CloudDesktopSelf-hosted
On this page
Navigated to
The navigated_to step is emitted by the recorder when the page navigates on its own — after a click, a form submit, or a redirect. On replay it does not force a load; it waits for the browser to arrive at the recorded destination.
In a workflow, this is a step object with "type": "navigated_to". Steps run in order, and each step can read the outputs of the steps before it. See the fullworkflows 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 |
|---|---|---|
url | string | The URL the recording arrived at; replay verifies against it. |
Example
A single navigated_to step as it appears in a workflow's steps array:
{
"type": "navigated_to",
"config": { "url": "https://example.com/dashboard" }
}How it behaves
- You rarely write this by hand — the recorder emits it to keep replay in step with the site.
- Use navigate when the workflow itself must force a URL; navigated_to only observes one.
Where it runs
The navigated_to step executes wherever the run executes. On yourlocal 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 usagewallet.
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.