Skip to content

Classification notification events

Classification notification events are produced when the result of a boolean classification changes state for a row.

They allow external systems to react when an important condition becomes true or false. This is useful when integrations depend on business state transitions rather than raw data changes.

Examples include:

  • a person becoming an adult
  • a contract becoming active
  • a booking becoming confirmed

Classification events detect state transitions, not continuous conditions.

Event list

Each classification notification event monitors:

  • one source table
  • one boolean classification
  • a specific state transition

When the classification result changes from the configured starting state to the configured target state, a notification event is emitted.

External systems receiving the event can then retrieve additional data through the API if needed.

Trigger conditions

Classification events are triggered by changes in classification outcomes.

Possible classification states include:

  • true
  • false
  • null

The null state represents the absence of the classification result and may occur when:

  • a row is created
  • a row is deleted
  • the classification definition changes

Event triggers are defined as state transitions from one state to another.

Examples:

From To Meaning
false true Condition becomes true
true false Condition becomes false
any true Condition becomes true regardless of previous state
null true Condition becomes true when a row first appears

Using transitions ensures that notifications are emitted only when the state changes, avoiding repeated notifications while the condition remains the same.

Payload specifics

Classification events generate the standard notification payload.

The payload typically contains:

  • the webhook identifier
  • the identifiers of affected rows

The payload does not contain full row data. Receiving systems are expected to retrieve detailed information through the API when needed.

Notes and limits

Several characteristics apply to classification notification events:

  • only boolean value classifications are supported
  • events are evaluated per row
  • notifications are emitted only when the classification state changes
  • the event itself does not define delivery behavior

Delivery behavior is determined by the webhook configuration associated with the event.

How-to

Related concepts