Glossary: WebhookGlossary

A webhook is an HTTP callback function triggered by specific events.

When such an event occurs in a service, the webhook makes an HTTP POST request to the URL configured when the webhook was created, with the POST request containing information about the event. This allows one application to notify another application when something of interest happens, enabling automated workflows and integrations. For example, when a candidate’s information in an ATS (application tracking system) is updated or when a new deal in a CRM (customer relationship management) application is created, a webhook can notify a client application about it.

Webhooks make it simpler for an application to stay up-to-date with changes in the data or state of a SaaS provider. Before webhooks, a client application would have to continually poll a SaaS provider to keep up with any changes to its data or state.

Webhooks work in the following fashion:

• The developer configures a webhook by specifying the URL of the endpoint in their application that will receive an HTTP POST when a certain event occurs.
• When the specified event occurs in the SaaS application, it sends an HTTP POST request containing information about the event in its payload to the URL defined in the configuration step above.
• The application receiving the HTTP POST request processes the data in the request’s payload and performs any necessary actions in response. These actions could include updating its records, sending notifications to end users, or triggering further processes.