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. from a Data Query node and apply a condition to it to execute a child node or branch.

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.

Each Decision Branch node requires at least one output. You define one or more conditional outputs and, optionally, a default output when no condition matches. Each output connector has a customizable label on the canvas so you can 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.

Per-output properties

For each output you add (except the default output), you configure the following.

Output label: Type an informative name for the branch. The label appears on the output connector on the canvas. You can keep the default placeholder text or enter a short name that describes what the branch does.

Add a Condition: Define one or more conditions that determine when this output runs. The node evaluates outputs in order and follows the first output whose conditions are all true. For each condition, specify what to evaluate (a metric A measurement or data point that is monitored and analyzed to detect anomalies and generate incidents., key, variable, or other field), a comparison operation, and a value. The available options depend on the data forwarded by the preceding node (e.g. Data Query, Transform, Trigger, or HTTP Request).

Forward data (in the advanced section): Choose whether to forward all rows from the input or only the rows that match the condition. This controls what data downstream nodes receive on this branch.

The data format (Summarized or Time Series) is determined by the preceding node and is not set in the Decision Branch.

If you add a default output, it runs when no other output's conditions match. The default output does not have conditions or a forward-data option.

Runbook Compatibility

Incident, Lifecycle, On-Demand, External (Webhook), and Subflow