# Group many events into one digest

> Group many events into one digest: 0 companies fully do it, 4 with a limit, 4 carry the tag. Every listing in Notifications with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/notifications.digest-batch/
- Markdown: https://www.anchorterminal.com/niches/notifications.digest-batch/index.md (~1,100 tokens)
- Slim: https://www.anchorterminal.com/niches/notifications.digest-batch/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/notifications.digest-batch/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 4 | 4 | 6 | 2 |

## 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.

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

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.

- **Courier (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.
- **Knock (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.
- **Novu (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.
- **SuprSend (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.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Pingram (Pingram)**: A BATCHED delivery status exists, but no digest or batching guide was found in the pages read.

- not this job: Amazon SNS (Amazon Web Services, Inc.): No digest step; PublishBatch only groups up to 10 publishes into one request.
- not this job: Expo Push Notifications (650 Industries, Inc.): No digest or batching of events; batching means up to 100 messages per request.
- not this job: Firebase Cloud Messaging (Google LLC): No digest or batching of events.
- not this job: MagicBell (MagicBell, Inc.): No digest or batch step in the API; workflow commands are broadcast, pause, wait and abort.
- not this job: ntfy (ntfy LLC): No digest or batching step; scheduled delivery and sequence-id updates replace one message, they do not group events.
- not this job: OneSignal (OneSignal, Inc.): No digest or batching step in the docs indexes; frequency capping and throttling limit sends rather than group them.
- not this job: Pushover (Pushover, LLC): No digest or batching feature in the API.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/notifications.digest-batch.json, or the MCP tool get_use_case with id notifications.digest-batch. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
