{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/notifications.send-user-event/",
    "json": "https://www.anchorterminal.com/niches/notifications.send-user-event/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/notifications.send-user-event/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/notifications.send-user-event/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 3 | 4 | 27 | 15 | 4 |\n\n## What counts as done\n\nOne trigger call with an idempotency key produces the in-app, push and email messages the workflow names for that user, with a run or message id returned and a retry within the key's window sending nothing twice; a list of recipients goes in one call.\n\nHow agents ask for it: notify the user their order shipped; send this alert by in-app and email; trigger the comment notification workflow\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Courier (trycourier.com, Inc.)**: One send takes a template, an array in to, optional routing to pin channels, and an Idempotency-Key that returns the original response on retry; it returns a requestId that is the message id.\n- **Knock (Knock Labs, Inc.)**: POST trigger takes up to 1,000 recipients with per-recipient data, an Idempotency-Key honoured for 24 hours, a cancellation_key, and returns workflow_run_id; channel steps fan out to in-app, push, email, SMS and chat. acc-28 wanted a bulk trigger across workflows, which Knock still lacks.\n- **SuprSend (SuprStack Inc)**: POST /trigger/ takes up to 100 recipients, or an array of up to 100 workflow records returning a 207 with per-record outcomes and message_id; an idempotency key holds 24 hours and a multi-channel node fans out across channels.\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- **MagicBell (MagicBell, Inc.)**: POST /broadcasts takes up to 1,000 recipients with per-channel overrides and returns the broadcast id; workflows run via POST /workflows/runs. Idempotency-Key (24 hours) is honoured on some endpoints, and the docs do not list which.\n- **Novu (Noti-Fire Apps Ltd.)**: POST /v1/events/trigger takes up to 100 recipients and returns a transactionId; bulk trigger takes 100 events. The Idempotency-Key (24 hours) works only after support enables it for the organisation.\n- **OneSignal (OneSignal, Inc.)**: One create call reaches up to 20,000 aliases with an idempotency_key kept 30 days and returns an id, but target_channel picks one channel per call; push plus email needs two calls or a Journey. acc-26 saw target_channel email ignored by the Node SDK.\n- **Pingram (Pingram)**: POST /send to one user carries email, in-app, SMS, call, web push and Slack payloads, forceChannels to pick channels, and returns a trackingId. No idempotency key, and one user per call; lists go through broadcasts.\n\n- not this job: Amazon SNS (Amazon Web Services, Inc.): A topic publish fans out to email, SMS, push and HTTPS subscribers, but there is no user, workflow or in-app model, and deduplication exists only on FIFO topics, which deliver to SQS.\n- not this job: Expo Push Notifications (650 Industries, Inc.): Push relay only; no in-app feed, email, workflows or idempotency key.\n- not this job: Firebase Cloud Messaging (Google LLC): Push transport only, with no in-app feed, email, workflows or idempotency key.\n- not this job: ntfy (ntfy LLC): Topic pub-sub with no recipient ids, workflows, in-app feed or idempotency key; one publish goes to whoever subscribed to the topic.\n- not this job: Pushover (Pushover, LLC): Push to Pushover's own app only; no workflows, in-app feed, email channel or idempotency key.\n\n## What stops agents finishing\n\n- workflow must exist in a dashboard before a trigger can name it\n- channel providers (email, SMS) configured and paid separately by the owner\n\n## Around it\n\nBefore: commerce.order-event, webhooks.receive-event. After: notifications.check-delivery.\n\n## Where this comes from\n\nWeight 15 of 100 in Notifications: 4 accounts (acc-26 to acc-29) on OneSignal, Knock and Courier, all builders; held up because it is what the five workflow listings sell\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/notifications.send-user-event.json, or the MCP tool get_use_case with id notifications.send-user-event. 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": "Send one product event to an app user across channels",
        "url": ""
      }
    ],
    "description": "Send one product event to an app user across channels: 3 companies fully do it, 4 with a limit, 27 carry the tag. Every listing in Notifications with the reason and a source.",
    "facts": null,
    "h1": "Send one product event to an app user across channels",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/notifications.send-user-event/",
    "published": "",
    "section": "agents",
    "title": "Send one product event to an app user across channels | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/notifications.send-user-event/"
  },
  "tokens": {
    "markdown": 1250,
    "slim": 280
  },
  "version": 1
}
