Notify¶
Angelia delivers in two directions. Push sinks call something when a release lands. Pull consumers ask for what they missed, whenever they wake up. Both read the same event log.
| Use it when | Page | |
|---|---|---|
| Webhook | you own an HTTPS endpoint: a CI server, n8n, a Lambda, your own bot | Webhooks |
| GitHub dispatch | a GitHub Actions workflow should run: tests, an update PR, an agent | GitHub Actions dispatch |
| Chat and push | humans should know: Slack, Discord, Telegram, ntfy, Gotify, Matrix | Chat and push |
| Pull API and SSE | the consumer has no public URL, or must never miss an event after downtime | Pull API and SSE |
| MCP | an AI agent should ask what changed, or watch something new | AI agents (MCP) |
The three pieces, once more¶
sinks: # where
- name: ci
kind: webhook
config: { url: https://ci.example.com/hooks/angelia, secret_env: CI_WEBHOOK_SECRET }
watches: # what
- name: fastapi
source: pypi
coordinates: { name: fastapi }
subscriptions: # which events go where
- name: fastapi-to-ci
sink: ci
filter: { package: fastapi }
Delivery guarantees¶
- At least once. Deduplicate on the event
id(or, for webhooks, thewebhook-idheader). - Retries with exponential backoff and jitter, about eight attempts over a day;
429and5xxare retried, other4xxand every redirect are permanent. - Dead letters stay visible and replayable:
angelia delivery list --status dead
angelia replay --delivery 01JC... # one delivery
angelia replay --subscription fastapi-to-ci --since 24h --dry-run
- One slow sink never blocks another: each delivery has its own retry state.