Notifications & automation

Reloqui pushes what matters to where your team already works, and lets operators run guarded actions on demand.

Subscriptions & channels

Create a subscription per project (Connect → Notifications) choosing a channel type and the events you care about:

Channel	Delivery
webhook	HMAC-signed `POST` (`X-Reloqui-Signature-256`), 3-attempt retry, delivery log.
slack	Human-readable message to a `hooks.slack.com` incoming webhook.
teams	Message to a Teams incoming webhook.
email	Via your configured SMTP settings.

POST /api/v1/webhooks/outbound/subscriptions
{ "projectId": "proj_…", "channelType": "slack",
  "url": "https://hooks.slack.com/services/…",
  "eventTypes": ["release.published", "release.rolled_back", "release.approval.suspended"] }

Release lifecycle (release.created|reconciled|published|rolled_back), approvals (release.approval.requested|approved|rejected|suspended), evidence (evidence.classified), ops alerts and daily digests. See the event taxonomy.

Delivery guarantees

Deliveries are dispatched by the outbox relay, signed, retried up to three times with backoff, and every attempt is recorded in the delivery log (visible in Operations). Failed deliveries surface as ops alerts.

Digests & ops alerts

Daily digest — a per-tenant summary of the last 24h of release activity (opt in via subscription event types).
Ops monitor (hourly) — emits ops.dlq.alert, ops.delivery.failures, and ops.connector.silent when something needs attention.

Self-service actions

The actions catalog exposes guarded, auditable operations any operator (or automation via a service token) can run:

GET  /api/v1/actions
POST /api/v1/actions/{actionId}/run   { "params": { "releaseId": "rel_…" } }

Built-in actions: reconcile-release, rescore-release, regenerate-notes, sync-connector, replay-dlq. Each returns a jobId and writes an audit entry, with per-action RBAC.

Operations guide · Notifications feature reference