Runbook Node Compatibility Matrix

This topic shows which runbook nodes Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. can be used in each runbook type. Use the matrix to confirm that a node is supported in an Incident, Lifecycle, On-Demand, External, or Subflow runbook. The matrix also provides the documented node execution value for usage and licensing. For an introduction to runbook nodes, see Runbook Nodes. For categories and how to add nodes, see Runbook Node Categories and Assembling runbook nodes.

Runbook types in the matrix

The matrix has five runbook types as columns, plus an additional column for External runbooks that are created in Aternity (Embedded in Aternity).

• Incident: Runbooks that execute automatically when a new incident is created.

• Lifecycle: Runbooks that execute automatically when a triggering lifecycle event occurs on an incident.

• External: Runbooks that trigger in response to a configured API call.

  • Aternity ISD: These runbooks are External runbooks but the editor shows a truncated set of nodes.

• On-Demand: Runbooks that trigger as required (either on-demand, or as scheduled).

• Subflow: Reusable chunks of automation that perform frequently used functions (e.g. open a ticket in an external system) and can be used to implement integrations with third-party systems.