Group@1

Node Group@1 is a purely structural, no-op container. It groups a set of nodes under a name so the graphical editor can collapse and hide them — like a named subroutine or region. It has no effect on the pipeline data or execution: running nodes inside a Group is identical to listing them inline. The only purpose of this node is to organize a pipeline visually.

Adapter Prerequisites

• General availability: All adapters support this node type.

Node Configuration

For common fields, see Overview. The grouped nodes are placed in the node's own transformations array and run, in order, on the same data context.

Configuration Properties

Property	Type	Required	Description
name	string	No	Display name of the group, shown as its label in the editor
description	string	No	Optional longer description
transformations	array	No	The grouped child nodes, executed in order on the same context

Example: Grouping field-setup nodes

transformations:
- type: Group@1
  name: Set status field
  transformations:
    - type: SetPrimitiveValue@1
      targetPath: $.status
      value: active
      valueType: String
    - type: Logger@1
      message: "status set"

Behavior Notes

• Group@1 is a no-op: it never reads or writes data and never branches. Grouping nodes vs. listing them inline produces identical pipeline runs.
• Children run on the same data context (like If@1/Switch@1), so JSONPath aliases such as $.full inside an iteration resolve exactly as they would without the group.
• Groups can be nested (a group inside a group).
• The node carries an x-nodeKind: "group" hint in the generated pipeline schema so the editor can render it as a collapsible region.