Niches · Event delivery & webhooks

Wake an agent when an event arrives

Four or more companies' docs show a full fit.

4companies, full fit
6companies, fit with a limit
7companies carry the tag
14share of the category's work
6first-hand accounts

What counts as done

Each event starts or reaches precisely one agent run with the payload, signed and verifiable, and a run that fails can be retried from the stored event without asking the sender to resend.

How agents ask for it: run the agent when a PR comment lands, start a review on every new pull request, send the approval back to my running agent, react to CI failing

Does the job 4

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

ListingWhy
Convoy C
Frain Technologies Inc.
A source receives the event, and a signed delivery to the agent's endpoint carries X-Convoy-Idempotency-Key; failed deliveries retry from the stored event by API without the sender resending. source
Hookdeck A
Hookdeck Technologies Inc.
Each received event is delivered once per connection to the agent's destination with an HMAC signature, and a failed one is retried from the stored event, by hand or by rule, without the sender resending. source
Upstash QStash BB
Upstash, Inc.
Each published message goes to the agent endpoint once per Upstash-Deduplication-Id, signed with a JWT in Upstash-Signature, and a failed one moves to the DLQ, retried by API from the stored message. acc-17 uses it as an out-of-the-box queue. source
Webhook Relay C
AppScension Ltd
A bucket receives the event, forwards it to the agent's public or localhost destination with durable retries, and failed deliveries are retried or replayed from the stored request without the sender resending. source

Does the job, with a limit 6

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
402cron B
Georgi Kalchev (operator, a named person; no company named)
Each firing is a signed delivery with a stable X-402cron-Delivery-Id and POST /api/tasks/{id}/run reruns it, but triggers are schedules only and no stored event log exists to replay from. source
Ably BB
Ably Realtime Ltd
An outbound webhook fires per channel message and can be signed with HMAC over the body, but a failed delivery is retried at most twice after a timeout and cannot be replayed from a stored event. source
Amazon EventBridge BB
Amazon Web Services, Inc.
A rule starts one target per matching event, and an archive replays stored events to the bus, but HTTPS targets are unsigned and the target has 5 seconds to answer. source
Hook0 B
FGRibreau SARL
An event the app posts is delivered signed to the agent's endpoint and can be replayed with hook0 replay, but only for events the app itself sends to Hook0; third-party events need code in front. source
PubNub BB
PubNub Inc.
An Events & Actions listener can call a webhook per message or presence event, but the Free tier doesn't retry, no request signature or stored-event replay was found. source
Svix BB
Svix Inc.
A message the app creates is delivered signed to the agent's endpoint and can be resent by API from the stored message, but only for events the app sends to Svix. source

Doesn't do this job 2

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

ListingWhy
Centrifugo C
Centrifugal Labs LTD
Proxy calls fire on client connect, subscribe and publish, not on outside events, and nothing is stored for replay. source
Pusher Channels D
MessageBird UK Limited
Webhooks fire only on channel existence, presence and client events; there is no stored event to replay a failed run from. source

What stops agents finishing

  • agent runtime has no public URL to receive the call
  • approval or event only reachable by long polling

Around it

Before: code.pull-request-opened. After: code.open-pr, human-in-the-loop.approval.

Where this comes from

Weight 14 of 100 in Event delivery & webhooks: 6 of 40 accounts, all people building their own triggers; none used a listed product for it

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

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.