{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/notifications.digest-batch/",
    "json": "https://www.anchorterminal.com/niches/notifications.digest-batch/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/notifications.digest-batch/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/notifications.digest-batch/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 4 | 4 | 6 | 2 |\n\n## What counts as done\n\nEvents 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.\n\nMeasured, for our own tests: the digest goes out within 60 seconds of the window closing.\n\nHow 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\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Pingram (Pingram)**: A BATCHED delivery status exists, but no digest or batching guide was found in the pages read.\n\n- not this job: Amazon SNS (Amazon Web Services, Inc.): No digest step; PublishBatch only groups up to 10 publishes into one request.\n- not this job: Expo Push Notifications (650 Industries, Inc.): No digest or batching of events; batching means up to 100 messages per request.\n- not this job: Firebase Cloud Messaging (Google LLC): No digest or batching of events.\n- not this job: MagicBell (MagicBell, Inc.): No digest or batch step in the API; workflow commands are broadcast, pause, wait and abort.\n- 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.\n- 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.\n- not this job: Pushover (Pushover, LLC): No digest or batching feature in the API.\n\n## What stops agents finishing\n\n- digest window capped by plan (Novu Free keeps delays to 1 day)\n- digest lost when the subscriber record is re-created\n\n## Around it\n\nBefore: notifications.send-user-event. After: email.send.\n\n## Where this comes from\n\nWeight 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\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Group many events into one digest",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": null,
    "h1": "Group many events into one digest",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/notifications.digest-batch/",
    "published": "",
    "section": "agents",
    "title": "Group many events into one digest: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/notifications.digest-batch/"
  },
  "tokens": {
    "markdown": 1100,
    "slim": 280
  },
  "version": 1
}
