> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudcruise.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Start

> Entry point of every workflow

The **Start** node is where every run begins. The browser opens on its `url`, and execution follows the node's `to` edge. Every workflow has exactly one Start node.

## Parameters

| Parameter | Type | Required | Description |
| - | - | - | - |
| `url` | string | Yes | URL the browser opens when the run starts. Supports variables |

## Examples

### Static Start URL

```json theme={null}
{
  "id": "b7e9a2f1-3c4d-4a8b-9e1f-2d3c4b5a6789",
  "name": "Open login page",
  "action": "START",
  "parameters": {
    "url": "https://app.example.com/login"
  }
}
```

### Dynamic Start URL

Open a page derived from a workflow input:

```json theme={null}
{
  "id": "b7e9a2f1-3c4d-4a8b-9e1f-2d3c4b5a6789",
  "name": "Open order",
  "action": "START",
  "parameters": {
    "url": "https://app.example.com/orders/{{context.inputs.order_id}}"
  }
}
```

## Edges

Start uses a single `to` edge pointing to the first node:

```json theme={null}
{
  "edges": {
    "start-node-id": { "to": "first-node-id" }
  }
}
```

## Notes

* A run is rejected when the URL resolves to an empty or invalid value, for example because an input variable it uses is missing
* Pick a start URL on the same origin as the requests or pages the workflow needs first. This matters for [API Flow](/concepts/workflow-dsl/api-flow) nodes, which send requests from the page the browser is on
* To open additional pages later in the run, use [Navigate](/concepts/workflow-dsl/navigate) or [Tab Management](/concepts/workflow-dsl/tab-management)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.