Decision Branch
Pass data in to this node
Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations.
Use as many Decision Branch nodes Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. in your 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. as you need, but be careful to avoid creating branches that produce contradictory, redundant, or confusing results. The Runbook Editor will not prevent you from defining unproductive branches.
Each Decision Branch node requires at least one child node or "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.". This can be either the True path or the False path, but, for clarity and consistency, it is a good practice to define both paths, even if one is only a stub. Each output connector has a customizable label shown on the canvas to help you annotate and keep track of what each branch does.
The Decision Branch properties are context-sensitive, based on the data forwarded by the immediately preceding node.
Properties
Node Label: Type an informative name for the Decision Branch node. You can keep the system-provided default of "Decision Branch" if you wish.
Debug: Select Debug if you want to receive debug data when the node executes.
Add An Output: Add a branch to the decision branch. Execution of the decision branch will stop at the first branch that evaluates to true.
Add A Default Output: Add a default output branch. This branch will execute if none of the conditions evaluate to true.
Runbook Compatibility
Incident, Lifecycle, On-Demand, External (Webhook), 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.