Webhooks allow you to subscribe to events that happen in your Height workspace. When an event gets triggered, we'll send a HTTP POST payload to your configured URL.
Webhooks are useful for setting up integrations, syncing a database with Height tasks, triggering workflows in other services, and more.
Webhook events payload are formatted in JSON. See more:
The webhook event object
Webhook event types
Webhooks will only send objects that are accessible to all members of a workspace. This means that private tasks will be redacted, and their activities will not be sent.
A webhook endpoint should return a HTTP status code 2xx if the webhook was correctly handled. This will let us know we shouldn't retry sending the event.
All webhook events are sent through a POST request with a
If your server isn't reachable, or isn't returning a correct status code, Height will try resending the webhook again up to 5 times within 3 days.
Height doesn't guarantee events will be ordered, and your service should take this into account.
In the unlikely event we don't receive your endpoint response while sending you a webhook, we may try resending the same webhook event later. Your service should be designed to handle duplicate events from Height webhooks.