---
schema_version: "1"
id: 3e66fa2eb467c671db987d6a75db1fdca105d1ee2307e3897a88e2d65adcc96b
title: Group
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/rpa-builder/6.6/toolbox-flow-control-group.md
canonical_url: https://docs.mulesoft.com/rpa-builder/6.6/toolbox-flow-control-group
source_site: docs.mulesoft.com
content_type: documentation
content_hash: ff58b18ab8e43d26a2c89e512f31af50b1639b09fd884107ab40bc59c1aac914
description: MuleSoft Documentation Site
release: "6.6"
latest: false
---
---
product: RPA Builder
version: 6.6
---

# Group

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Using the _Group_ block gives you a clearer overview when designing your Workflows. It provides
delineation both graphically and in terms of content within a Workflow. For example, you can easily
use it to group Action Step variables.

You can, however, also use all other Action Steps. A couple of exceptions are the _Transaction_
Action Step and the _Workflow Initialization_ element. It is possible to position multiple _Group_
blocks inside each other.

The _Group_ block does **not** restrict the availability of variables in subsequent transactions
such as the _Transaction_ Action Step, for example.

## Properties

The _Group_ block has no properties.

## Inbound Variables

The _Group_ block possesses no inbound variables.

## Outbound Variables

The _Group_ block possesses no outbound variables.