Learn · Integrations
Webhooks both ways
Take posts in from your tools, and send signed notices out to your systems.
Checked against the product on · written for people writing code
Posts coming in
A webhook feed gives you a URL. Any tool that can post JSON becomes a data source.
Add a feed of the webhook kind and copy the URL.
Set a signing secret and give the same secret to the sending tool.
The signature is checked before the body is read.
Name a field the payload must carry.
A post missing that field is rejected at the door, so a misrouted tool fails loudly.
Send a test post and read the live tail.
Notices going out
Automate
Webhooks
| Endpoint | Events | Signing secret | Last delivery |
|---|---|---|---|
| https://ops.example.com/dmz | review.held, review.approved | Set | 200 · 12 seconds ago |
| https://example.com/audit | ledger.appended | Set | 200 · 1 minute ago |
Open Webhooks and select Add endpoint.1
Pick the events the endpoint subscribes to.2
The delivery log records every attempt and its response code.
Read the signature line and verify every delivery before you trust the body.3
| Event | Sent when |
|---|---|
| A call was held | A rule proposed a sensitive action and a person is needed. |
| A review closed | A person approved, changed, or declined a held action. |
| A fix was dispatched | An approved action left the platform for your systems. |
| An entry was written | The logbook gained an entry. |
| A standing changed | A watched thing moved between allowed, take a look, and block. |