Event data

2026-09-03Last updated

Event data is the contextual information that accompanies every event. It can be used to add conditions to automation triggers and to contextualize automation responses. Different types of data are available depending on the type of event.

Event source data

The event source (source entity) corresponds to the origin of the event. It is available for most event types.

For a list of all the event types available for each type of entity, see Event types.
Note:
Not all event types are available in Security Center SaaS.

Event data as variables

When the Variable x. button is visible, you can use variables to reference event data such as:
  • {Source.Id}: The unique identifier (GUID) of the source entity.
  • {Source.Name}: The name of the source entity.
  • {SourceDescription}: The description of the source entity.
  • {EventDescription}: The message that accompanies the event. The included data varies depending on the event type.

Event location data

The event location is only available for certain event types, such as events associated to a Patroller unit, or events associated to a record type (Record updated and Record fusion events, for example).

Event data for access control events

Most access control events have three types of available data:

  • Doors
  • Cardholders
  • Credentials
Note:
For door events, the source entity must be a door () or an access point (), but you can add cardholders and credentials as conditions.

Event data for ALPR events

ALPR events, such as License plate read and License plate hit, have a variety of data available to use as conditions. You can view the available event data by clicking Add condition.
Available conditions for a "License plate hit" event.

For more information, see Adding conditions when creating event-to-actions for license plate reads.

Note:
ALPR is only available through federation.

Event data for camera and custom events

Camera, video analytics, and custom events treat event data as a text message, instead of being exposed as specific conditions.

You can evaluate the event data with the Message condition using the following operators:

  • equal to
  • not equal to
  • contains
  • starts with
  • ends with
  • in
  • not in
  • similar to
  • not similar to
  • evaluates to

For more information, see Special operators for event conditions.

Except for the evaluates to operator, all other operators assume that the event data (Message) contains a single value.

Automation trigger configuration for 'Face recognized' event using the Message condition.
Best Practice:
When a specific condition already exists for an event, such as gender and age for the Face recognized event, use the specific condition instead of configuring it using the Message condition.