Subflow Runbooks

A subflow A reusable automation chunk that performs frequently used functions, such as opening a ticket in an external system, and can be used to implement integrations with third-party systems. is a reusable sequence of runbook An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook. nodes Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. that performs a discrete activity. Unlike incident, lifecycle, on-demand, or external (webhook) runbooks, a subflow is not triggered on its own. It is invoked from another runbook when that runbook reaches a Subflow node. The calling runbook passes context into the subflow and receives output when the subflow completes.

Each subflow has a single entry point (Subflow Input) and ends with Subflow Output. Subflows can be used in any runbook type (incident, lifecycle, on-demand, or external) as long as the nodes inside the subflow are compatible with that context. The same subflow can be reused in multiple runbooks.

Subflows are created and edited in the same Runbook Editor as other runbooks. For how to create, use, and manage subflows, see Subflow Overview.