Webhook
A mechanism by which one system automatically sends an HTTP request to a chosen URL the moment a defined event occurs, pushing data instead of waiting to be asked.
In more detail
A webhook flips the usual request model. Instead of automation repeatedly asking a system whether anything has changed, the system pushes a notification, an HTTP request to a URL you provide, the instant a defined event occurs. It is the difference between being told when something happens and having to keep checking.
Webhooks are the backbone of event-driven automation because they make it timely and efficient: work runs when there is something to react to rather than on every poll. The trade-off is that the receiver must be reliable and able to handle bursts, and must treat incoming webhook data as untrusted until verified.
Where this shows up at Ceven
Ceven workflows can be triggered by webhooks from the connected tools, so a process runs the moment its triggering event fires rather than on a delayed schedule. That real-time reactivity is what lets a Ceven workflow respond to an incoming message, a new record, or a status change as it happens, with the trigger recorded in the audit trail.