Group many events into one digest
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
Events with the same key inside the window produce one message listing every event, urgent events marked to skip go out at once, and a pending digest can be cancelled by key.
Measured, for our own tests: the digest goes out within 60 seconds of the window closing. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: send one summary instead of ten emails
, batch these comments into a daily digest
, hold low-priority alerts for an hour
Does the job, with a limit 4
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Courier B trycourier.com, Inc. | Journey Batch node groups by category key and releases on max items, a quiet window (1 minute to 1 day) or a max wait up to 7 days; topic digests run on schedules. Cancel tokens are set in journey settings, and acc-29 could not set one on API-built journeys. source |
| Knock A Knock Labs, Inc. | Batch step groups by batch_key over fixed, dynamic or sliding windows up to 90 days, and batched items cancel by cancellation_key. No per-event skip is documented, only flushing the first item at once. source |
| Novu B Noti-Fire Apps Ltd. | Digest groups by subscriber plus one aggregation key, regular or scheduled windows, can start only when events repeat, critical skips it, and cancel works by transactionId. Digests cap at 1 day on Free, and acc-15 lost a digest after a subscriber was re-created. source |
| SuprSend BB SuprStack Inc | Batch groups by recipient and batch key over fixed, dynamic or relative windows with Flush first item immediately, and a pending run cancels by idempotency_key. No per-event skip of the batch is documented. source |
Couldn't check 1
The docs were closed to us, or silent. These carry no mark either way.
Doesn't do this job 7
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Amazon SNS BB Amazon Web Services, Inc. | No digest step; PublishBatch only groups up to 10 publishes into one request. source |
| Expo Push Notifications B 650 Industries, Inc. | No digest or batching of events; batching means up to 100 messages per request. source |
| Firebase Cloud Messaging BB Google LLC | No digest or batching of events. source |
| MagicBell C MagicBell, Inc. | No digest or batch step in the API; workflow commands are broadcast, pause, wait and abort. source |
| ntfy C ntfy LLC | No digest or batching step; scheduled delivery and sequence-id updates replace one message, they do not group events. source |
| OneSignal BB OneSignal, Inc. | No digest or batching step in the docs indexes; frequency capping and throttling limit sends rather than group them. source |
| Pushover C Pushover, LLC | No digest or batching feature in the API. source |
What stops agents finishing
- digest window capped by plan (Novu Free keeps delays to 1 day)
- digest lost when the subscriber record is re-created
Around it
Before: notifications.send-user-event. After: email.send.
Where this comes from
Weight 6 of 100 in Notifications: 1 account (acc-15) plus acc-09 wanting periodic progress digests; vendor pages for Knock, Novu, Courier and SuprSend fill the rest
The same as data: /api/v1/use-cases/notifications.digest-batch.json, or the MCP tool get_use_case with id notifications.digest-batch. Other jobs in this category: /api/v1/niches?category=notifications.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.