Skip to main content
Groups records by a field value. This controls how downstream action nodes process records — creating one action per group instead of one batch for all records. It’s also required before Aggregation to define what to aggregate over.

​
Configuration

SettingDescription
FieldThe field to group by

​
Common grouping strategies

Group byEffect
Primary key (e.g., Contact.Id)One action per record
Category field (e.g., Account.Industry)One action per category

​
How It Works

1

Choose a field

Select the field that defines how records should be grouped (e.g., group by Account ID, Region, or Status).
2

Connect downstream nodes

Action nodes after this will create one action per group. Aggregation nodes will compute summaries per group.

​
Output

The data itself is unchanged — Group By only sets grouping metadata. Downstream nodes use this metadata to process records in groups rather than as a single batch.
Without a Group By node, action nodes (Slack, Email, Create Record, etc.) produce a single batch action for all records, with field values concatenated. Add Group By to control granularity.

​
Example

Send one Slack message per account (instead of one batch message):
  1. Group By → Salesforce.Account.Id
  2. Slack → message template with account details
Without Group By, Slack would send one message listing all accounts.

​
Best Practices

  • Group by primary key when you need per-record actions (updates, notifications, record creation)
  • Group by category field when you need per-category summaries or actions
  • Always use Group By before action nodes if you want per-record behavior
  • Use Split Group later in the workflow to remove grouping
  • Aggregation — compute summary statistics per group (SUM, AVG, COUNT)
  • Split Group — remove grouping to return to single-batch processing
  • Sort — order records within groups