Subflow
The catalog exposes Subflow-shaped nodes, but the current runtime does not dispatch a child flow, create a nested run, or return child output.
Subflow
The catalog still contains two subflow-shaped nodes:
| Node | Slug | Current meaning |
|---|---|---|
| Start Subflow | startSubflow | A child-shaped start node that identifies the graph as subflow-shaped. |
| SubFlow | subflow | A parent utility node that can map inputs and expose a local result shape. |
Current limitation: The runtime does not dispatch the selected child graph, create a nested child run, or return child execution output through outputData. Treat both subflow nodes as unavailable for nested execution until the runtime changes.
What the current node does
The subflow function does not look up or execute the selected child ActionFlow. It copies the non-reserved inputs it receives into a local object, returns that object as outputData, and sets status to skipped. That local outputData is mapped input data, not a child flow's output. The function does not create a child run-history row, child queue item, or child triggerSource record.
The subflow value is the compatibility/display source for subflow-shaped execution paths, but its presence does not dispatch a child or enable nested execution.
Use a supported path instead
To run a child today:
- Save the child as a normal Start graph in Actionflow Studio.
- Start it with
POST /api/runs, the TypeScript SDK, hosted MCP, or its flow webhook. - Correlate the returned
runIdorqueueIdwith the parent if you need to coordinate work.
If a parent must initiate the child, invoke the supported API or webhook path from a backend or an explicit HTTP integration and handle the identifiers and output yourself. Do not wire a SubFlow node as if it synchronously returns child output. There is no supported outputData child-result contract today.
Related
API
Start a saved Start-compatible ActionFlow with POST /api/runs, including authentication, request options, validation timing, and queue handoff.
Artifacts
Distinguish generated ActionFlow artifacts, uploaded run files, Knowledge Base files, and Agent artifacts, including the limits the current runtime enforces.