Trigger
Choose the saved start shape for Actionflow Studio, API, webhook, scheduled, and subflow-shaped runs without creating a new trigger type.
Trigger
Every supported ActionFlow has one start node. The start node is the graph's entry point; the trigger surface supplies the run context around that saved graph.
| Start node | Use |
|---|---|
| Start | Actionflow Studio, dashboard, API, SDK, and hosted-MCP runs |
| Start Scheduled | A recurring, weekly, or one-time clock |
| Start Subflow | The catalog's subflow-shaped start, currently not a working nested-dispatch feature |
The current runtime does not dispatch a child graph for a Subflow node. Treat the subflow-shaped nodes as unavailable until nested execution is implemented; use a supported Start, API, or webhook path instead.
API and webhooks do not add a start type
An API call or flow webhook runs a saved Start-compatible graph. It does not create an API, Webhook, or other fourth start node, and it does not change the graph's saved start node. The request adds a run envelope and records a triggerSource such as api or webhook.
Use a graph with a Start node for an on-demand or inbound integration. Use Start Scheduled only when the scheduler owns the entry point.
triggerSource
The current source values are:
| Value | Meaning |
|---|---|
manual | Actionflow Studio or dashboard execution |
api | Default for an authenticated API-key run |
webhook | An inbound flow webhook |
schedule | A scheduled tick |
subflow | Compatibility/display source for subflow-shaped execution paths; it does not dispatch a child or make nested execution work |
unknown | A missing or unrecognized source shown by the product |
An API request may carry a canonical triggerSource, but the REST boundary does not reject a non-canonical string, so the table is the supported vocabulary rather than an enforced enum. The authenticated API-key context selects the default (api for an API key and manual for a session). The subflow value is the compatibility/display source for subflow-shaped execution paths, not evidence that a child was dispatched. Do not use a source value to change authorization or to make a Subflow run execute.
Run input keys
When a run needs an input override, the key is:
{nodeId}_{inputName}- Actionflow Studio Flow Inputs uses this form for empty required fields.
- REST uses
payload.inputs, and the TypeScript SDK usesinputs, with the same key shape. - A flow webhook's JSON object is copied into the webhook run's
inputs; use the key shape when the value should override a node input. The complete request is also available through the trigger envelope.
The input key format does not change the start-node type. See Flow execution model for the distinction between saved values, run inputs, and request-envelope fields.