# Wake an agent when an event arrives

> Wake an agent when an event arrives: 4 companies fully do it, 6 with a limit, 7 carry the tag. Every listing in Event delivery & webhooks with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/webhooks.trigger-agent/
- Markdown: https://www.anchorterminal.com/niches/webhooks.trigger-agent/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/webhooks.trigger-agent/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/webhooks.trigger-agent/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

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 4 | 6 | 7 | 14 | 6 |

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

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

- **Convoy (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.
- **Hookdeck (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.
- **Upstash QStash (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.
- **Webhook Relay (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.

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

- **402cron (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.
- **Ably (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.
- **Amazon EventBridge (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.
- **Hook0 (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.
- **PubNub (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.
- **Svix (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.

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

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

As data: https://www.anchorterminal.com/api/v1/use-cases/webhooks.trigger-agent.json, or the MCP tool get_use_case with id webhooks.trigger-agent. 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
