Manual
Use the Start node to run a saved graph from Actionflow Studio, the dashboard, or POST /api/runs; Manual is not a separate trigger type.
Manual
The Start node (start) is the default entry for a saved graph that is run on demand from Actionflow Studio, the ActionFlow dashboard, the REST API, the TypeScript SDK, or hosted MCP. There is no separate API or webhook start-node type.
Add it
- Open Actionflow Studio for a new or existing ActionFlow.
- Choose Start from the start-node picker.
- Save the graph before relying on API, SDK, or webhook execution.
A supported flow has one start node. The graph itself defines the nodes and edges; the caller only supplies run-specific inputs and a trigger envelope.
Run paths
| Path | What happens | triggerSource |
|---|---|---|
| Actionflow Studio | Use Run flow and fill the fields shown under Flow Inputs when needed. | manual |
| Dashboard | Start the saved flow from the flow list or overview. | manual |
| REST / SDK / hosted MCP | The same saved Start-compatible graph is sent to POST /api/runs. | api for an API key or manual for an authenticated session by default |
API and webhook callers do not add a new node or change the saved start node. The canonical triggerSource values are manual, api, webhook, schedule, subflow, and unknown; see the Trigger overview for their meanings. See API and Webhook.
Inputs
Empty required fields exposed by Actionflow Studio use the run-form key:
{nodeId}_{inputName}For REST, send the key in payload.inputs; the SDK calls the same field inputs. A trigger envelope with body, headers, query, and method is merged onto the saved Start node separately. See Flow execution model for the current input and mapping order.
API and webhook ingress validate the saved graph before the caller's run inputs are merged into the execution copy. A run input therefore does not bypass a required-input validation error on the saved graph; save the value, connect the required named handle, or fix the graph before retrying.
When to use another start
- Start: on-demand, API-triggered, SDK-triggered, and webhook-triggered integrations.
- Start Scheduled: the platform should fire the graph on an interval, weekday, or one-time timestamp. See Scheduled.
- Start Subflow: the catalog shape exists, but the current runtime does not dispatch a child graph. Treat it as unavailable and use a separate supported API or webhook invocation. See Subflow limitation.
Related
Trigger
Choose the saved start shape for Actionflow Studio, API, webhook, scheduled, and subflow-shaped runs without creating a new trigger type.
Scheduled
Configure recurring, weekly, and one-time ActionFlow schedules with IANA timezones, DST-aware wall-clock calculations, missed-run behavior, and independent scheduled runs.