Sub-flow Entry
The Sub-flow Entry node marks the start of a recipe that is meant to be called by another recipe’s Sub-flow Call. When the parent recipe invokes this one, the child session starts at the Sub-flow Entry and follows the next port into the body of the sub-flow.
Configuring the node
There is nothing to configure. The Sub-flow Entry has no editable settings — its only role is to act as the canonical starting point for a callable sub-flow. The drawer shows a brief explanation.
Variables passed in from the parent recipe are mapped on the parent side, via the Sub-flow Call node’s input-variable mappings. The Entry node does not declare its own input contract.
Output port
- next — fires immediately when the sub-flow is invoked. Wire it to the first real node of the sub-flow body.
Where it’s used
A recipe authored to be reusable starts with a Sub-flow Entry (instead of the usual Start node) so that other recipes can call into it via Sub-flow Call. Top-level recipes that customers reach directly via triggers use Start; sub-flow recipes use Sub-flow Entry.
Best practices
- Use one Sub-flow Entry per callable recipe. Multiple entries are not supported.
- Pair Sub-flow Entry with at least one Sub-flow Exit so the parent’s
on_returnport can fire cleanly.
See also
- Sub-flow Call — invokes this sub-flow from a parent recipe.
- Sub-flow Exit — returns control to the parent.