Start Node

The Start Node is the entry point of a flow. Every flow has at least one.

What it serves

The engine begins executing a flow at the Start Node. The label on this node defines the entry the agent is wired to in /org.

When to use it

• Always — every flow file needs at least one Start Node.
• A flow file can contain multiple Start Nodes if it serves multiple entries (e.g. Project-Start, Project-Weather, Project-Test); each one is a separate pipeline anchored to its own Start Node.

Connections

• Outputs only. No input dot.
• Can be rotated to face whichever direction makes the canvas readable.

Settings

Field	Required	Purpose
Node Label	Yes	The entry name. One word, capital first letter. Must match the Start Node value configured in /org/agents/<agent> for the main entry.
Node Description	No	Free-text help for other developers reading your flow. Doesn't affect execution.

Naming rules

When a Start Node is the main entry point for an agent:

• The agent's /org config has a Start Flow field (e.g. Project) and a Start Node field (e.g. Start).
• The flow file on disk must be named <StartFlow>.flow.json (e.g. Project.flow.json).
• The Start Node's label inside the file must equal the Start Node value from /org.

If any of these don't line up, the engine won't find the entry.

What it looks like in the compiled flow

{
    "id": "startNode_6N8CbNmtrtYU5BRbKhmkK7o_8lto34IN",
    "type": "startNode_",
    "data": { "label": "startNode_", "settings": { "label": "Start" } }
}