Throttle Step
Limit notification frequency for recipients
The throttle step limits how often a recipient can receive notifications from a workflow. If a notification would exceed the throttle limit, it is dropped.
Configuration
| Setting | Description |
|---|---|
| Duration | The throttle window duration |
| Unit | The time unit: seconds, minutes, hours, or days |
Use Cases
Prevent notification spam
Limit promotional notifications to once per day:
Trigger → Throttle (1 day) → Channel (Email) → EndIf the workflow is triggered multiple times for the same user within 24 hours, only the first notification is sent.
Rate limit alerts
Prevent alert fatigue by throttling system notifications:
Trigger → Throttle (1 hour) → Channel (Push) → EndHow It Works
- When execution reaches a throttle step, it checks if the recipient received a notification from this step within the throttle window
- If within the window: the workflow stops, notification is not sent
- If outside the window: execution continues to the next step
- The throttle timestamp is recorded for future checks
Throttle vs Batch
| Throttle | Batch |
|---|---|
| Drops excess notifications | Combines notifications into one |
| Only first notification sent | All events included in digest |
| Use when you want to limit | Use when you want to aggregate |
Throttle example: User gets one "new follower" push per hour, extras are dropped.
Batch example: User gets one email with all new followers from the past hour.
Combining Steps
You can combine throttle with other control steps:
Trigger → Batch (10, 1 hour) → Throttle (4 hours) → Channel (Email) → EndThis batches events for up to an hour, then ensures the user doesn't receive more than one batched notification every 4 hours.