Skip to main content

⚙️ Talos Workflows & Alarms

Workflows are the "brain" of Talos. They define exactly how an incoming alarm should be handled—whether it's automatically closing a test signal or guiding an operator through a high-priority burglary response.

🏗️ How Workflows Lifecycle Works​

An alarm is always processed for a specific site. Talos searches for a matching workflow in this priority order:

  1. Site Level (Most specific)
  2. Site Group
  3. Global/Company Level (Default fallback)

🛠️ Step-by-Step: Creating a Workflow​

  1. 1

    1. Define Incoming Conditions​

  2. 2

    Set the "Triggers" that activate the workflow:

  3. 3
    • Alarm Code: (e.g., BA for Burglary).
    • Schedule: (e.g., Only run during "After Hours").
    • Logic: Use "All of" (AND) for strict matching or "One of" (OR) for broad categories.
  4. 4

    2. Add Decision Nodes​

  5. 5

    Ask the system (or the operator) a question:

  6. 6
    • Automated Check: Is the site currently armed?
    • Manual Check: Does the video show a human presence?
  7. 7

    3. Configure Actions​

  8. 8

    What should happen next?

  9. 9
    • Notifications: Send an automated SMS or Email.
    • Commands: Trigger a siren or lock a door.
    • Escalation: Move the alarm to the priority operator queue.
  10. 10

    4. Close and Log​

  11. 11

    Every workflow must end with a Closing Status (e.g., "False Alarm," "Police Dispatched"). This ensures cleaner reporting and audit trails.

📋 The Operator Alarms Page​

The Alarms page is the central cockpit for monitoring staff.

Located on the Left Side. This list shows all unassigned alarms that have arrived but haven't been picked up by an operator yet.

💡 Pro-Tip: Automated vs. Manual​

Related Articles

Understanding Workflows

The link between GCXONE users and Talos roles.

Site Management

Configuring the targets for your workflows.

Next: Managing Sites in Talos