Subscriptions

A subscription watches a repository for changes and delivers a webhook when matching write operations land — it is WarmHub’s mechanism for automation. A subscription watches its own repository by default, or a different repository in the same org (a cross-repo subscription); either way, the webhook is delivered using the subscription’s home repo for credentials and configuration.

Create a subscription

POST to your webhook when Signal writes land (things or assertions):

wh sub create signal-hook --repo myorg/myrepo --on Signal --kind webhook \
  --filter '{"shape":"Signal"}' --webhook-url https://example.com/hook

When a matching write lands, WarmHub records an action event, matches it against every active subscription’s filter, and dispatches the webhook to each match — retrying transient failures with exponential backoff before the run goes terminal. See Creating Subscriptions for the webhook payload and credential binding.

Next Steps

Need	Page
Create a subscription and see the webhook payload shape	Creating Subscriptions
Watch a different repository in the same org	Cross-Repo Subscriptions
The filter grammar that selects which writes fire	Filter JSON
Bind delivery auth and verify WarmHub’s HMAC signature	Credentials & Signatures
List, view, pause, resume, update, or delete subscriptions	Managing Subscriptions
Inspect the delivery feed and per-attempt details	Delivery Feed
Understand run statuses, retries, and dead-letter behavior	Run Statuses
Delivery-outcome notifications (failures and opt-in success)	Notifications