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.
Trigger
An ActionFlow has one start node. That node is how the graph begins. There is no trigger-type dropdown on a generic start.
| Start node | When to use |
|---|---|
| Start | Studio, dashboard, and API / SDK / MCP runs |
| Start Scheduled | Recurring, weekly, or one-time clock |
| Start Subflow | A parent graph calls this flow |
Inbound HTTP from a third party is a Webhook on a Start graph. It is not a fourth start-node type.
Chat in Slack, Discord, Teams, or email is an agent trigger, not a flow start node.
Related
Node settings
The right-hand inspector in Actionflow Studio. Edit a selected node's inputs, credentials, mapping, and requirements without a separate test runner.
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.