Skip to main content
The Event service maintains an append-only record of all organizational activity. It serves as the primary communications bus that triggers automated workflows and records audit trails.

​
Key responsibilities

  • Event Ingestion: Receives events from webhooks, agents, workflows, and manual triggers.
  • Ledger Storage: Appends events to a chronological, immutable log.
  • Subscription Dispatching: Broadcasts new events to active workflows and listening systems.
  • Event Replay: Supports querying and replaying historical logs for analysis.

​
Events vs state

Events record observations of what happened. They are distinct from entities, which record the current state of a resource. For instance, multiple events might log individual modifications to a task, while the Entity service tracks the final status of that task.