Digest mode and rate limiting

When a workflow fires frequently - like on every new row - you can get a flood of notifications. Digest mode and rate limiting prevent this.

Rate limiting

Every workflow has a rate limit that caps how often it can fire per hour. The default is 100 executions per hour.

You can adjust this in the workflow settings. If the limit is reached, additional triggers are queued until the next hour window opens.

Digest mode

Digest mode batches multiple trigger events into a single notification. Instead of sending 50 Slack messages when 50 rows arrive, digest mode collects them and sends one summary message on a schedule.

Enable digest mode

1. Open your workflow in the editor.
2. Toggle Digest mode on.
3. Set the digest schedule (e.g., every 15 minutes, hourly, daily at 9 AM).
4. Save the workflow.

How it works

1. When the trigger fires, instead of executing steps immediately, the event is stored as "digest pending"
2. At the scheduled digest time, all pending events are bundled together
3. The workflow steps execute once with a summary of all batched events
4. The pending events are cleared

When to use digest mode

• Row ingested triggers on high-volume datasets - batch into a "New data summary" message
• Action event triggers when many actions change at once - send a daily roundup instead of individual alerts
• Any workflow where real-time notification isn't critical

Execution states

When digest mode is active, you'll see these execution statuses:

Status	Meaning
digest_pending	Event captured, waiting for the next digest window
queued	Ready to execute at the next digest time
running	Currently executing steps
completed	All steps finished successfully
failed	A step encountered an error

Next steps

• Monitor your workflow executions to verify digests are working
• Review trigger types to choose the right trigger