A webhook subscription sends a client organisation's events to a web address you choose, as each one happens.
- 1
Under Outbound webhooks, choose the Organisation whose events to send.
- 2
Enter the Target URL. It must be https, to a named host: never http, an IP address or a local name.
- 3
Tick the Events to send, and choose Add subscription.
The subscription is listed with its organisation, its events, its Failures and its Status.
What is sent
Each event is posted to the address as JSON: the event's name, when it was sent, and the request or project it is about. Today Kelvin sends four of the events listed, all for changes made through the Kelvin API, by a client's Deployr or another system holding a key:
- engineering_request.created and engineering_request.updated, when a request is raised or changed.
- engineering_project.created and engineering.change, when a project is created or changed.
The other events can be ticked, but nothing sends them yet.
Deliveries
- Kelvin tries a delivery up to 3 times. An attempt with no answer within 10 seconds fails, and a redirect isn't followed.
- Recent deliveries lists the newest 20, refreshed every 30 seconds, each Delivered or Failed with the response code, its attempts and when it was sent.
- Failures on a subscription counts its failed deliveries since the last one that went through.
- Failed deliveries also appear in the event margin.
Note
A subscription can't be edited or removed on this screen yet. To change one, write to hello@sentorotech.com.au.