Event-driven automation
Automation that runs in response to events emitted by systems as they happen, rather than on a fixed schedule that repeatedly checks for changes.
In more detail
Event-driven automation reacts to things as they happen. When a system emits an event, a new record, a status change, an incoming message, the workflow runs in response, often within seconds. This is the opposite of polling, where automation repeatedly asks has anything changed on a timer, and only notices changes at the next check.
The event-driven approach is more timely and often more efficient, since work happens only when there is something to do rather than on every poll. Its dependency is that the source system must actually emit events, usually via a webhook. When it does not, polling remains the fallback, at the cost of latency and wasted checks.
Where this shows up at Ceven
Ceven workflows can be triggered by events from the connected tools, so a process runs the moment its trigger fires rather than waiting for the next scheduled check. Where a source system does not emit events, a scheduled trigger fills the gap. Either way, what started the run is recorded alongside every step in the audit trail.