---
schema_version: "1"
id: 0b4e8815e12749d5124effcee0e44ae88915eb6486e35fb8d6f1be61cd769d1d
title: Group
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/rpa-builder/latest/toolbox-flow-control-group.md
canonical_url: https://docs.mulesoft.com/rpa-builder/latest/toolbox-flow-control-group
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 34957ac620adcc1f89f966f89b17aeb5ecee444800538cd45d03cc4477ceda2a
description: MuleSoft Documentation Site
release: "6.7"
latest: true
---
---
product: RPA Builder
version: 6.7
is-latest-version: true
---

# 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.