The Start node is one way to begin a workflow. It serves as the default entry point and is triggered manually or programmatically. Every workflow requires at least one Start node—use Set as Default Start when the workflow has multiple Start nodes to define which one runs by default.
Unqork provides three ways to begin a workflow:
- Start node: the default entry point. Triggered manually by an end-user or programmatically by another workflow or component.
- Timer Start node: triggers automatically on a schedule. Supports relative, exact, and cron-based timing.
- Signal Start node: triggers when a specific signal event is received from another workflow or an external source.
Note: For time-based starts, see Timer Start Node. For event-based starts, see Signal Start Node.
How to read settings tables
The tables below describe each configurable option as it displays in the Unqork IDE. Values are formatted as follows:
inline code— a value to type exactly as shown | Bold — a value selected from a drop-down, radio button, tab, or choice chip | ON/OFF — toggle state | ✓ — checkbox checked | ☐ — checkbox unchecked
Settings
| Setting | Field | Type | Default | Description |
|---|---|---|---|---|
| Label | label |
Text input | — | A display name for the node. |
| Path | nodeId |
Text input | — | The unique identifier automatically generated for the node. Preset and not editable. |
| Set as Default Start | default |
Toggle | OFF | When set to ON, this setting marks this node as the default entry point when multiple Start nodes exist. |
Changelog
| Date | Change |
|---|---|
| — | Initial publication. |