Webhooks
A webhook lets one system notify another when an event happens instead of waiting for repeated polling.
Also called: webhook, event callback
Definition
A webhook is an event-driven HTTP notification sent from one system to another when a defined event occurs.
Why it matters to the business
Webhooks can reduce delay and repeated checking when an operational workflow needs to react quickly to a new lead, booking, status change or record update.
How it works
The source system sends a request to a receiving endpoint. The receiver validates the request, records the event and starts the agreed downstream action.
Where it appears in real systems
Common examples include form submissions, CRM record changes, payment events, booking events and support-system updates.
Common failure modes
- The sender retries and creates duplicate processing.
- The receiving endpoint is unavailable.
- Authentication or signature validation fails.
- The event arrives before dependent data is ready.
Implementation considerations
- Authenticate or validate the sender.
- Make processing idempotent where duplicate delivery is possible.
- Log failures and retry behavior.
- Define what happens when downstream systems are unavailable.
When it is appropriate
Use webhooks when the source platform can reliably push the event and the workflow benefits from event-driven response.
When it is not appropriate
Polling can be simpler when the source has no reliable webhook support or the workflow does not require prompt reaction.
Relationship to BYFORCE
Webhooks can appear in Integration Sprint and Lead Response implementations when the source platform supports them.