Subflow Output Runbook Node

The Subflow Output node Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. marks the end of 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.'s execution path and defines where the subflow's output A document containing data sets generated by the execution of a runbook, including output of queries and reports from point products, as well as output of analysis or other runbook nodes. is generated. This node serves as the termination point for a subflow, allowing the subflow to pass data back to the parent 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. that called it.

Every subflow must end with at least one Subflow Output node. When a subflow executes, it processes data through its sequence of nodes and when execution reaches a Subflow Output node, the subflow completes and returns control to the parent runbook. The data that the subflow returns is determined by the output variables that were defined in the Subflow Input node's "Context Values Sent Back To Caller" section.

If your subflow has multiple execution branches (for example, if it contains Decision Branch nodes that create separate paths), you may add a Subflow Output node to the end of each branch. Having multiple Subflow Output nodes allows each branch to complete independently and return its results to the parent runbook.

When a subflow is used in a runbook, the Subflow Output node connects to the node that follows the subflow in the runbook's execution flow. The output variables defined in the Subflow Input node are then available in the subflow node editor's Output tab, where you can map them to variables in the parent runbook for use in subsequent nodes.

Properties

Node Label: Type an informative name for the Subflow Output node. You can keep the system-provided default of "Subflow Output" if you wish.

How Subflow Output Works

The Subflow Output node does not require configuration of output variables itself. Instead, the output variables that the subflow returns are defined in the Subflow Input node's "Context Values Sent Back To Caller" section. These variables must be defined as subflow scope variables in the Variable Definition Editor before they can be used.

When the subflow executes, any subflow scope variables that are listed in the "Context Values Sent Back To Caller" section of the Subflow Input node will have their current values passed back to the parent runbook when execution reaches a Subflow Output node. The parent runbook can then access these values through the subflow node's Output tab, where the output variables can be mapped to runbook variables for use in subsequent nodes.

For more information about how subflows work and how to use them in runbooks, see Working with Subflows.

Runbook Compatibility

Subflow