Skip to content
Let ideas be heard and improvements last.
Gemy

Glossary

What is Webhook?

A short definition of Webhook, how it is applied on the floor and where it lives in the product.

Short definition
Webhook: Software sending a short notification to a set address on its own when an event happens (record closed, action overdue); telling instead of being polled.

How is it applied?

The company chooses which event sends a notification to which address; the receiving system verifies the notification and triggers its own work. Outgoing data is kept to a minimum and the address and signature are managed by an authorised person. Fictional example: when an action becomes overdue, a webhook sends the record number and event type to the company's ticketing tool. If more detail is needed, the receiver reads it through an authorised API. A webhook is often confused with an API. With an API the receiver asks; with a webhook the sender reports when the event happens.

In the product

In the product outgoing webhooks go to the company's address for selected events and Teams notification cards work as masked cards; both are installed off and the company switches them on with approval. Every outbound connection stays off until the company enables it.

Cookies

Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.

Cookie policyPrivacy notice