Home
Setup guide
Install and connect your Security Center SaaS application.
System automation
Converting event-to-actions to automations
You can convert legacy event-to-actions to automations using the Automation task.

Pre-deployment guide
Review requirements, order, and activate your Security Center SaaS system.
Setup guide
Install and connect your Security Center SaaS application.
- Getting started
- User management
- Device management
- System automation
  - What is system automation?
    System automation in Security Center SaaS is a workflow to trigger actions based on schedules or events. It helps administrators manage repeatable tasks with less effort, so they can focus on higher‑value work.
  - Overview of automation entities
    To trigger a series of actions manually, on a schedule, or based on events in your system, you can set up automation entities.
  - Examples of system automation
    Administrators can use system automation to reduce effort when handling repeatable tasks in Security Center SaaS. These tasks include responding to device and security issues and performing routine system maintenance.
  - About events
    An event is a record of an activity or incident that occurred in the system. Security personnel can monitor events in real time and investigate them later. Events can also trigger automations in the system.
  - About schedules
    A schedule is an entity that defines a set of time constraints that can be applied to a multitude of situations in the system. Each time constraint is defined by a date coverage (daily, weekly, ordinal, or specific) and a time coverage (all day, fixed range, daytime, and nighttime).
  - Creating schedules
    To define a set of time constraints for a multitude of situations, such as when a user can log on to the system or when video from a surveillance camera can be recorded, you can create schedules and then apply them to specific entities.
  - Adding audio files
    You can add new audio files that can be played when users receive an alarm in Security Center SaaS, or used with the Play a sound action.
  - About automation entities
    An automation entity is a repeatable process in Security Center SaaS. It consists of two parts: a trigger that defines what starts the automation, and a response that defines the actions that follow.
  - Creating an automation entity
    Before setting up an automation, you must create it as an entity in Configuration desktop.
  - Configuring automation triggers
    When configuring an automation, you must first define what triggers it.
  - Configuring automation responses
    After you define the triggers, define the actions that run when the automation is triggered.
  - Advanced settings for automation entities
    Configure the automation’s scope, activation periods, and other advanced options on the Advanced settings page.
  - Adding automations to maps
    To allow Security Center SaaS operators to manually trigger automations directly from the maps, you can add automations to maps as map objects.
  - Event data
    Event data is the contextual information that accompanies every event. Event data can be used to add conditions to automation triggers and to contextualize automation responses.
  - Contextualized actions
    For event‑based automations, you can use data from the triggering event to contextualize the response actions. With contextualized actions, a single automation can handle multiple automation scenarios.
  - About threat levels
    A threat level is a predefined scenario that you activate for a specific area or the entire system to manage special situations, such as a business event or emergency evacuation. Activating a threat level triggers a series of actions tailored to the scenario. Deactivating the threat level returns the system to regular operation.
  - Defining threat levels
    To help your security personnel respond quickly to a specific scenario, you can define a threat level.
  - Threat level scenario: Fire
    A scenario for creating threat levels is in case of a fire.
  - Threat level scenario: Gunman
    A scenario for creating threat levels is in case of a gunman.
  - Converting event-to-actions to automations
    You can convert legacy event-to-actions to automations using the Automation task.
  - Converting scheduled tasks to automations
    You can convert legacy scheduled tasks to automations using the Automation task.
User guide
Perform daily operations and monitor your facilities in the Security Center SaaS application.
Genetec ClearID
Set up and use ClearID in Security Center SaaS.
Federation
Set up and use Federation in Security Center SaaS.
Appliances
Install, configure, and use your cloud-managed appliances.
Supported devices
Review the supported devices list.
Supported features
Review the supported features list.
Technical support
Learn how and where to find support to help you solve technical issues.
Glossary

Converting event-to-actions to automations

2026-02-09

You can convert legacy event-to-actions to automations using the Automation task.

What you should know

Legacy event-to-actions can be converted to event-based automations.

Note:

An event-to-action cannot be converted to an automation in the following situations:

When the Use source time zone option is enabled.
This option applies when the server that manages the source entity of the event is in a different time zone than the main server.
When the action requires synchronization with the access control unit for offline I/O linking.
This situation occurs when the Trigger output action is used with one of the following events:
- Door closed
- Door opened
- Door forced open
- Door open too long
- Request to exit
- Request to exit normal

Procedure

Open the Automation task and click the Actions tab.
Select one or more event-to-actions and click Convert to automation.

Note:
You’re limited to 100 event-to-actions at a time. If none of the selected event-to-actions can be converted, the Convert button is hidden.
Click Convert > Close .
You’re automatically brought to the Automations page.
Note:
- The created automations are named after the source event, the "For" condition (if any), and the action name.
  Syntax: EventName (ForCondition) > ActionName
- The converted event-to-actions are kept as backups, but deactivated to prevent duplication of performed actions.
  If an event-to-action selected for conversion remains active after conversion, it means that it cannot be converted.
- If a converted event-to-action was deactivated before conversion, the corresponding automation created is also deactivated.
- Automations converted from event-to-actions trigger and execute actions with the privileges of the user who performed the conversion.
(Optional) Configure the advanced settings for the created automations.

After you finish

Test the created automations before permanently deleting the converted event-to-actions.