Start
The single point where a workflow run begins.
Every workflow has exactly one Start node. When a run is triggered, execution begins here and the incoming data (the run's input) is handed to whatever node you connect next.
When to use it
You don't add a Start node for a particular task — it's the required beginning of every workflow. A workflow without a Start node can't run, and a workflow with more than one is invalid.
Inputs & outputs
| Input handle | None — nothing runs before Start. |
| Output handle | One. Connect it to the first node that should process the run's input. |
Parameters
The Start node has no parameters to configure.
What it passes downstream
The Start node emits the input payload for the run — the data the workflow was triggered with. For example, if the workflow is triggered by a new WooCommerce order, the order payload enters at Start and becomes the input of the next node.
Example
A workflow that syncs a WooCommerce order to NetSuite begins like this:
[ Start ] → [ Mapping: Woo order → NetSuite ] → [ Connection: NetSuite ] → [ End ]
The order payload arrives at Start, flows into the Mapping node to be reshaped, is sent to NetSuite via a Connection node, and the run finishes at End.
To see exactly what data is entering at Start, run a Test Run and click the Start node to inspect its output.