Coalesce

The Coalesce nodeClosed Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. merges multiple input datasets into one output dataset. Use it when you want to combine data from several branches (for example, after a Merge node) for display, structured variables, or further processing.

All inputs must have the same kind of data in the first row (all summary, or all time series). The editor anchors on the first row in the Inputs list. It treats that row as summary data or time series data, and only lets you pick matching sources for the other rows.

Placement in the graph

The Coalesce node must have exactly one parent. The runbook editor reports an error if more than one node is wired into the Coalesce node.

Properties

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

Inputs

Inputs: Configure one or more rows. Use Add Input to Coalesce to add a row. Drag the handle on a row to change order. Order matters when more than one row could supply the same metric for the same keys (see How data is merged): the higher row in the list (closer to the top) takes precedence.

Each row has a source type and, when needed, a secondary value. The editor offers Parent, Specific Node, Runtime Variable, and Incident Variable as source types, filtered by runbook variant as described below.

  • Parent: Use the output of the node that is wired directly into the Coalesce node. The second control shows Uses immediate parent. At most, one row may use Parent, and Parent is only available when the node has a parent connection.

  • Specific Node: Use the output of another upstream node. The list includes ancestor nodes in the graph, except the immediate parent (which Parent covers).

  • Runtime Variable and Incident Variable: Use a structured variable defined for the runbook. The second control lists variables for that scope.

Source types available by runbook variant:

  • Incident: Parent, Specific Node, Runtime Variable, Incident Variable.

  • Lifecycle, On-Demand, and External (Webhook): Parent, Specific Node, Runtime Variable.

  • Subflow: Parent, Specific Node, Incident Variable, Subflow Variable.

How data is merged

Every input must match the first row in the Inputs list: either all summary data or all time series data. If you add an input of the other kind, validation reports that one or more inputs have a different data shape (summary versus time series) than the first selection.

The editor treats each row as a set of keys plus metrics. Rows that share the same keys are merged into one output row. The output row includes every distinct metric that appears on any of the merged rows. If more than one row defines the same metric, the row higher in the Inputs list (closer to the top) takes precedence. Lower rows only add metrics that were not already supplied from above. The result matches the combined keys and metrics downstream nodes see when they use this Coalesce output.

If you reference a variable or node that was removed or is not valid for the runbook variant, validation reports that the source is no longer available or not allowed. You cannot use the Parent source on more than one row.

Runbook compatibility

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