Manual
Use the Start node to run a flow from Actionflow Studio, the dashboard, or POST /api/runs. Manual is the default start node, not a separate trigger type dropdown.
Manual
The Start node (start) is the default entry for a flow you run on demand: from Actionflow Studio, from the ActionFlow dashboard, or from the API.
Add it
- Open Actionflow Studio for a new or existing ActionFlow.
- Choose Start from the start-node picker (or the start category in Add node).
- A flow can have only one start node.
There is no "Trigger Type" menu on the node. Manual, scheduled, and subflow are different start nodes.
How a manual flow runs
| Path | What happens |
|---|---|
| Actionflow Studio | Use Start or Run flow. Empty required inputs can be filled in Flow inputs. |
| Dashboard | Run the flow from the flow list or overview. |
| API / SDK / MCP | POST /api/runs / runActionFlow / run_actionflow. See API. |
triggerSource is manual for studio and dashboard runs, and api when an API key starts the same graph.
Inputs
Define node inputs on the graph as usual. Empty required fields become run-form keys ({nodeId}_{inputName}). The same keys work in payload.inputs on Trigger Run.
When to use Start vs other starts
- Start: on-demand and API-triggered automations.
- Start Scheduled: the platform should fire the flow on an interval or one-time
runAt. See Scheduled. - Start Subflow: this graph is meant to be invoked by a parent Subflow node.
Inbound HTTP from a third party should use a flow webhook, not a second start-node type.
Trigger
How an ActionFlow starts. Use one start node (Start, Start Scheduled, or Start Subflow). Inbound HTTP is a flow webhook, not a start-node type.
Scheduled
Use the Start Scheduled node to run a flow on a recurring interval, a weekly weekday and time, or a one-time timestamp, with an IANA timezone.