Start
Controlled node
Overview
The Start node is the entry point for workflow execution. It automatically fires when a workflow begins running, triggering its output event to initiate the rest of your workflow.
This node requires no inputs and has no configurable properties—it simply listens for the workflow's initial run event and signals the start of execution through its fired output.
Output events
The Start node has a single output event:
- Fired: Emitted automatically when the workflow begins execution. Connect this event to other nodes to trigger your workflow logic.
Inputs
The Start node has no inputs.
Outputs
| Output | Type | Description |
|---|---|---|
| Fired | Event | Fires automatically when the workflow starts running. |
Runtime behavior and defaults
When a workflow execution begins, the Start node automatically receives the global run event. Upon receiving this event, it immediately triggers the fired output event without any processing or delay.
This node is typically placed at the beginning of your workflow and serves as the trigger for all subsequent operations. It does not consume any tokens or perform any data transformations.
Example usage
Basic workflow initiation
Connect the Start node's fired event to an AI Write node to begin text generation as soon as the workflow runs:
- Add a Start node to your workflow
- Connect the
firedevent output to theruninput of an AI Write node - When the workflow executes, the Start node automatically fires, triggering the AI Write node to begin generation
Multiple entry points While most workflows use a single Start node, you can use multiple Start nodes if your workflow has different initialization paths based on external events or conditions.