Subflow Input
This node
Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. is used to describe the input to a subflow. The starting entity Things deployed in the customer environment that are needed to run the business, such as applications, devices, interfaces, and locations. in the Subflow Input node is optional. Providing this field allows you to explicitly supply these details to give the 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. the context it needs to be able to execute, information that will be passed to the subflow from the 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..
Properties
Node Label: Type an informative name for the Subflow Input node. You can keep the system-provided default of "Subflow Input" if you wish.
Debug: Select Debug if you want to receive debug data when the node executes.
Starting Entity
Specify the object that will be passed to the subflow by choosing it from the dropdown menu.
Context Values Received From Caller
Specify the names of variables that will receive values from the parent runbook. Each variable must be defined separately in the Variable Definition Editor. When the subflow is used in a runbook, these variables are listed in the subflow node editor, and each must be given a value or mapped from a runbook variable.
You can add descriptions, validation, and allowed values for each input variable so that runbook authors see clear guidance when they configure the subflow. For details, see Configuring subflow parameters.
Context Values Sent Back To Caller
Specify the names of variables that will be passed out of the subflow to the parent runbook. Each variable must be defined separately in the Variable Definition Editor. When the subflow is used in a runbook, these variables appear in the subflow node editor's Output tab, where you can map each to a variable in the parent runbook.
You can add a description for each output variable so that runbook authors understand what each variable contains. For details, see Configuring subflow parameters.