Actions

An action is a single webhook delivery: when a write matches a subscription’s filter, WarmHub dispatches one to the subscription’s target. This section explains how those deliveries behave — the statuses a delivery moves through, when WarmHub retries, and what happens when one can’t get through. Reach for it when a webhook isn’t arriving or you need to know whether a failure will retry.

You inspect a subscription’s deliveries with wh sub log:

wh sub log signal-hook

Subscription: signal-hook
  succeeded 1/1 2m ago run 019d90f0-0000-7000-8000-000000000000 write ops[0]
  dead_letter 5/5 15m ago run 019d90e0-0000-7000-8000-000000000000 write ops[0]
    HTTP_503: Webhook responded 503

Next Steps

Need	Page
Run statuses, retry and backoff rules, error codes, and terminal fallback	Action Delivery Lifecycle
Inspect the delivery feed and per-attempt details for a subscription	Delivery Feed
Walk a failing subscription through a debug runbook	Debugging a Failing Subscription
The HTTP endpoints that return runs, attempts, and notifications	HTTP API → Actions