Runs onWrit CloudDesktopSelf-hosted
On this page
Navigate
The navigate step loads a URL in the real browser and waits for the page to settle before the next step runs. It is almost always the first step in a workflow.
In a workflow, this is a step object with "type": "navigate". 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 |
|---|---|---|
url required | string | The destination URL. Placeholders resolve at run time: {{key}} from the workflow’s declared inputs, {{vault:name}} for secrets. |
Example
A single navigate step as it appears in a workflow's steps array:
{
"type": "navigate",
"config": { "url": "{{url}}" }
}How it behaves
- Use a declared-input placeholder in the URL so the same workflow works across many pages.
- A navigation the page performs by itself (a link click, a redirect) is recorded as navigated_to, not as a second navigate.
Where it runs
The navigate 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.