Start Node
Every workflow has exactly one Start node. It defines how the workflow is triggered and emits trigger metadata to downstream nodes.
Start
ManualRun manually
Trigger types
| Type | When it fires |
|---|---|
| Manual | You click the Run button in the editor toolbar |
| Schedule | A cron-style timer fires (interval, daily, weekly, monthly, or custom cron) |
| Webhook | An external HTTP POST hits the workflow's unique URL |
See Scheduling for the full configuration reference for each mode, including the webhook URL setup, rate limits, and SSE stream endpoint.
Outputs
The Start node emits the following metadata to its downstream nodes, regardless of trigger type:
| Field | Description |
|---|---|
triggerType | "manual", "schedule", or "webhook" |
triggeredAt | ISO timestamp of when the run was kicked off |
executionId | Unique id of this run, useful for cross-referencing logs |
workflowId | Id of the workflow being executed |
The Start node has no inputs — it's the entry point. Webhook POST bodies are not currently forwarded to downstream nodes; use the webhook as a trigger and let the workflow fetch its own data.
Permissions
The Start node respects organization RBAC:
- Viewing and configuring a manual/schedule trigger requires workflow:update (owners, admins, and members who own the workflow).
- Viewing or regenerating the webhook URL requires workflow:execute — the URL itself acts as the execution credential, so the same role gate applies as actually running the workflow.
Next Steps
- Scheduling — full reference for manual, scheduled, and webhook triggers
- Workflows — building and running workflows end-to-end
- Executions — viewing run history and logs