Glossary
What is a webhook?
A webhook is an HTTP request one system sends to another as soon as an event happens, so the receiver does not have to poll for changes.
A webhook is an HTTP callback: when an event happens in one system, such as a new employee in an HRIS or a course completion in an LMS, it sends an HTTP POST with event data to a URL the receiving system registered. Webhooks give near real-time updates without constant polling.
How does it work?
- The receiver registers an endpoint URL and chooses which events to subscribe to.
- When an event occurs, the sender POSTs a payload, usually JSON, often with a signature header.
- The receiver verifies the signature, stores the event and responds quickly with a 2xx status.
- If delivery fails, most senders retry for a period of time; after that, the event may be lost.
Webhooks are usually paired with an API: the webhook says something changed, and the receiver calls the API to fetch the current, full record. That keeps payloads small and avoids acting on stale data.
Where it shows up in integrations
- HRIS to LMS BambooHR can call a webhook when monitored employee fields change, triggering provisioning in the LMS.
- LMS to HRIS LearnUpon-style completion events push training records back to HR or compliance systems.
- CRM sync A new or updated contact in the CRM triggers a matching update in the SaaS product.
Common pitfalls
- Doing slow work inside the request handler, causing timeouts and duplicate retries.
- Not verifying signatures, so anyone who finds the URL can inject events.
- Assuming exactly-once delivery: events can arrive twice or out of order, so handlers must be idempotent.
- Relying on webhooks alone with no scheduled reconciliation to catch missed events.