Batch Step

The batch step collects multiple trigger events and groups them into a single notification. This prevents notification overload when many events occur in a short period.

Configuration

The batch sends when either condition is met: the batch size is reached, or the timeout expires.

Use Cases

Activity digests

Instead of sending a notification for every comment, batch them:

Trigger → Batch (size: 10, timeout: 1 hour) → Channel (Email digest) → End

If a user receives 15 comments in an hour:

• First batch sends after 10 comments
• Second batch sends after 1 hour with remaining 5 comments

Reducing notification fatigue

Batch rapid events to avoid overwhelming users:

Trigger → Batch (size: 5, timeout: 30 minutes) → Channel (Push) → End

Template Access

When a batch step triggers, templates have access to the batched events. You can iterate over the batch in your template:

You have {{ batch.size }} new notifications:

{% for item in batch.items %}
- {{ item.data.message }}
{% endfor %}

How It Works

1. First trigger event starts a new batch
2. Subsequent triggers for the same recipient are added to the batch
3. When batch size is reached OR timeout expires, execution continues
4. The next step receives the batched data
5. A new batch starts for future triggers

Batch Key

Events are batched per recipient by default. This means each user has their own batch that collects their events independently.