Webhooks¶
The webhook sink POSTs the release event to an HTTPS endpoint, signed with
Standard Webhooks. It is the universal adapter: CI servers, workflow tools
such as n8n or Node-RED, serverless functions, your own service.
sinks:
- name: ci-webhook
kind: webhook
config:
url: https://ci.example.com/hooks/angelia
secret_env: CI_WEBHOOK_SECRET # or secret_ref: a stored secret
timeout: 10s
What the receiver gets¶
| Header | Value |
|---|---|
Content-Type |
application/cloudevents+json; charset=utf-8, or your template's type |
webhook-id |
<event id>:<subscription id>, identical on every retry and replay |
webhook-timestamp |
Unix seconds of this attempt |
webhook-signature |
v1,<base64 HMAC-SHA256>, one per active secret |
The body is the CloudEvent, or the subscription's template.
Receiving it¶
Rules for receivers:
- Require a signature. Reject unsigned requests: if someone removes the secret, only a strict receiver notices.
- Pass the raw body to the verifier, before parsing JSON.
- Deduplicate on
webhook-id. - Answer
2xxfast, do the work later. Answer503to have Angelia retry;401and other4xxare final. Never redirect.
Rotating the secret¶
The variable can hold up to three secrets separated by spaces. Add the new one on both sides, wait for in-flight retries, then drop the old one.
Example: trigger a Jenkins or Drone job¶
Point the sink at the CI's generic webhook trigger and let a small template shape the body: