Niches · Notifications

Send one product event to an app user across channels

Two or three companies' docs show a full fit.

3companies, full fit
4companies, fit with a limit
27companies carry the tag
15share of the category's work
4first-hand accounts

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 3

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

ListingWhy
Courier B
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. source
Knock A
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. source
SuprSend BB
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. source

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.

ListingWhy
MagicBell C
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. source
Novu B
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. source
OneSignal BB
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. source
Pingram C
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. source

Doesn't do this job 5

Listings in the category that do something else, with the reason.

ListingWhy
Amazon SNS BB
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. source
Expo Push Notifications B
650 Industries, Inc.
Push relay only; no in-app feed, email, workflows or idempotency key. source
Firebase Cloud Messaging BB
Google LLC
Push transport only, with no in-app feed, email, workflows or idempotency key. source
ntfy C
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. source
Pushover C
Pushover, LLC
Push to Pushover's own app only; no workflows, in-app feed, email channel or idempotency key. source

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

The same as data: /api/v1/use-cases/notifications.send-user-event.json, or the MCP tool get_use_case with id notifications.send-user-event. Other jobs in this category: /api/v1/niches?category=notifications.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.