Component Grouping in Editor

To keep your automation workflows clean and organized, Monkedo allows you to group multiple components together. By holding right-click and dragging a selection box in the editor, you can bundle selected components into a single, structured group.

However, to maintain the integrity and execution order of your automation, grouping must follow one strict rule: The selected components must form a single, isolated execution path.

A group must behave like a single component from the outside. This means the selected sub-graph must have exactly one starting component (initial entry) and exactly one ending component (final exit).

If your selection causes the workflow to split or merge outside the group's boundaries without a clear single entry and exit point, the grouping will fail.

1. Linear Flows (Valid)

Components connected sequentially in a straight line are fully eligible for grouping. The flow starts at one point and ends at another.

• Structure: A -> B -> C

• Can be grouped? Yes

2. Forking / Branching (Invalid)

If a single component splits into multiple parallel paths and those paths do not merge back inside your selection, you cannot group them. This creates multiple exit points.

• Structure: A -> B and A -> C

• Can be grouped? No

3. Merging / Joining (Invalid)

If multiple independent paths merge into a single component within your selection, it cannot be grouped because it creates multiple entry points.

• Structure: A -> C and B -> C

• Can be grouped? No

4. Closed Parallel Paths (Valid)

If your flow splits (forks) but completely merges back (joins) before exiting the selection, this is valid. The group still maintains exactly one entry point ($A$) and exactly one exit point ($C$).

• Structure: A -> B, A -> D, B -> C, D -> C

• Can be grouped? Yes

If you receive an error while trying to group components, quickly check your selection for the following:

• Does the selection have more than one component receiving inputs from the outside?

• Does the selection have more than one component sending outputs to the outside?

If the answer to either is yes, try expanding your selection to include the missing merging or splitting nodes until you have a clean Single Entry -> Single Exit structure.