Event-based automation triggers

Triggering events

An event-based automation requires at least one trigger. Each trigger is made up of at least one event and an associated event source (entity).

• Events originate from a source entity. You can specify multiple sources for the same event.
• Events can be generic or specific to certain entities.
• To eliminate the possibility of false alarms, events can be configured to occur more than once within a set time period before the automation is triggered.

For a complete list of events and their related entities, see Event types.

Trigger conditions

Conditions act as additional criteria that must be met before the automation is triggered. Some event types can be conditionalized depending on the type of event, event source, or available event data. For example, you can conditionalize an Access denied event by specifying which cardholders or credentials can trigger it.

For more information on the type of data available for each event, see Event data.

Multiple conditions can be used for a single trigger. They are combined using the AND operator.

The available operators and operand types depend on the type of condition. For example, you can specify that a cardholder belongs (in) or does not belong (not in) to a list of cardholders and cardholder groups.

For more information on the available operators, see Special operators for event conditions.

Trigger combinations and sequences

You can use multiple triggers in a single automation to represent complex scenarios.

• Triggers can be grouped and evaluated against each other. For more information, see Combining automation-triggering events using AND or OR.
• Trigger groups can be sequenced with a time limit for each transition. For more information, see Configuring events that need to occur in sequence.