Skip to main content
Events are immutable records of things that have happened. Every meaningful operation in your company generates an event. Thygon appends these events to a central, append-only organizational ledger.

​
Event structure

Each event contains core metadata and a custom payload. The structure provides total auditability for all processes.
FieldTypeDescription
idstringUnique identifier of the event.
typestringIdentifier representing the action (e.g., github.pr.created).
sourcestringSystem or tool that originated the event.
actorIdstringIdentifier of the actor who triggered the action.
timestampstringISO 8601 timestamp when the event occurred.
payloadobjectJSON payload containing event-specific data.

​
Example event

Here is an example of a support ticket event: 
{
  "id": "evt_9b1a8c7e6f",
  "type": "support.ticket.created",
  "source": "zendesk-integration",
  "actorId": "usr_human_4455",
  "timestamp": "2026-06-16T12:54:04Z",
  "payload": {
    "ticketId": "TCK-402",
    "subject": "Unable to change workspace settings",
    "priority": "high"
  }
}

​
Immutable ledger

Once an event is written to the ledger, you cannot edit or delete it. This design prevents tampering and ensures that you can deterministically replay event history to audit past actions or reconstruct organizational state.