# Send one product event to an app user across channels

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

- Canonical: https://www.anchorterminal.com/niches/notifications.send-user-event/
- Markdown: https://www.anchorterminal.com/niches/notifications.send-user-event/index.md (~1,250 tokens)
- Slim: https://www.anchorterminal.com/niches/notifications.send-user-event/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/notifications.send-user-event/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

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 3 | 4 | 27 | 15 | 4 |

## What counts as done

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

How agents ask for it: notify the user their order shipped; send this alert by in-app and email; trigger the comment notification workflow

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

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

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

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

- 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.
- not this job: Expo Push Notifications (650 Industries, Inc.): Push relay only; no in-app feed, email, workflows or idempotency key.
- not this job: Firebase Cloud Messaging (Google LLC): Push transport only, with no in-app feed, email, workflows or idempotency key.
- 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.
- not this job: Pushover (Pushover, LLC): Push to Pushover's own app only; no workflows, in-app feed, email channel or idempotency key.

## What stops agents finishing

- workflow must exist in a dashboard before a trigger can name it
- channel providers (email, SMS) configured and paid separately by the owner

## Around it

Before: commerce.order-event, webhooks.receive-event. After: notifications.check-delivery.

## Where this comes from

Weight 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

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

---

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