Node reference
Start
Begin a workflow run
Start is the entry point of a workflow. Its connections decide which nodes run first. Use a single run while learning; add a repeating schedule after the workflow produces the result you expect.
Try it step by step#
- Connect Start’s out port to a Variable node’s in port.
- In Variable, add message with the value Hello. Keep Start set to run once, then run the workflow.
- Inspect Start, then Variable. This shows the difference between the data Start creates and the data the next node creates.
What to expect#
Start emits an object with startTime, an ISO timestamp such as 2026-09-20T09:00:00.000Z. Variable then emits {"message":"Hello"}. Your timestamp will be different.
Things to check#
- A disconnected node will not run just because it is on the canvas.
- A schedule starts new runs. Wait pauses a path inside an existing run. See scheduling before choosing an interval.
Keep learning#
Parameters#
| Setting | Default | What it does |
|---|---|---|
| Run | once | Choose a single run, a repeating interval, or fixed daily run times. |
| Every | 10 | Number of interval units between scheduled starts. |
| Interval unit | seconds | Unit used by Every, such as seconds or minutes. |
| Start | now | Start the interval schedule now or from a chosen first-run time. |
| First run | (empty) | First-run date and time when starting the interval at a chosen time. |
| Daily times | ["09:00"] | Daily clock times for a fixed-time schedule. See Scheduling for the runtime timezone. |
Inputs#
No inputs ports.
Outputs#
| Port | Value | Description |
|---|---|---|
out | object | Workflow start time. |
out fields#
| Field | Type | Description |
|---|---|---|
startTime | string | ISO timestamp for this run. |