---
title: iluminr Automations
description: automation flows for critical communications
---

[Skip to content](https://help.iluminr.io/knowledge/iluminr-flow#main-content)

English

Show submenu for translations

![iluminr logo](https://help.iluminr.io/hs-fs/hubfs/iluminr%20logo.png?width=227&height=48&name=iluminr%20logo.png)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Log in to iluminr](https://login.catalysttech.co/)

[Log in to iluminr](https://login.catalysttech.co/)

 iluminr Knowledge Base

- There are no suggestions because the search field is empty.

1. [Knowledge base](https://help.iluminr.io/knowledge?hsLang=en)
2. [iluminr for Admin Users](https://help.iluminr.io/knowledge/iluminr-for-admin-users?hsLang=en)
3. [Alert Automations](https://help.iluminr.io/knowledge/iluminr-for-admin-users?hsLang=en#alert-automations)

# iluminr Automations

## Automate critical actions based on defined rules

### Overview

**iluminr Automations** is a powerful automation feature within the iluminr platform that enables organizations to streamline crisis communication and response workflows. By leveraging automated triggers, conditions, and actions, Automations ensure that critical alerts are detected, teams are notified, and response activities are activated without delay.

This functionality is particularly useful for automating incident communications, activating response teams, and ensuring that critical information reaches the right people at the right time.

---

#### Key Capabilities

- **Trigger-based automation**: Start work flows automatically when emails are received or conditions are met.
- **Conditional logic**: Apply rules to filter by sender address, subject line, or keywords.
- **Multi-action workflows**: Automatically notify contacts, activate teams, and send communications across multiple channels.
- **Rapid response activation**: Reduce delays by ensuring pre-defined messages and teams are immediately engaged.
- **Customizable flows**: Easily tailor flows to fit unique organizational needs and response procedures.

Once your automations are in place, take it even further with **[Scheduling and Activity Logs](https://help.iluminr.io/knowledge/get-to-know-schedules-rosters?hsLang=en)**

---

#### How iluminr Automations Works

### 1. Accessing Automation

1. Navigate to the **iluminr home screen**.
2. Select **Libraries → Automation**.  
   ![](https://help.iluminr.io/hs-fs/hubfs/image-png-Sep-03-2026-03-07-35-8160-AM.png?width=670&height=367&name=image-png-Sep-03-2026-03-07-35-8160-AM.png)
3. Choose an existing automation or select + Automation to begin building your new workflow
   
   ![](https://help.iluminr.io/hs-fs/hubfs/image-png-Sep-03-2026-03-09-59-5040-AM.png?width=670&height=120&name=image-png-Sep-03-2026-03-09-59-5040-AM.png)

### 2. Setting Triggers

- Select **Trigger Type: Email**.
  
  ![](https://help.iluminr.io/hs-fs/hubfs/image-png-Sep-03-2026-03-10-36-7248-AM.png?width=670&height=300&name=image-png-Sep-03-2026-03-10-36-7248-AM.png)
- Define the conditions for when the automation should begin.
- Workflows are designed to activate when an email is received at a designated address 
  
  ![](https://help.iluminr.io/hs-fs/hubfs/image-png-Sep-03-2026-03-13-32-8287-AM.png?width=670&height=539&name=image-png-Sep-03-2026-03-13-32-8287-AM.png)

**Received At:** Is the address you can add to the notification list from the source system you are expecting to receive the trigger notification. This is unique to each flow.

**Sender Email Address:** Can be used to add the email address you are expecting to receive the "trigger" notification from. This reduces the possibility of unwanted workflow activation.

### 3. Applying Conditions

Conditions decide which of the emails arriving at your trigger address actually start the workflow. You pick something to match on, pick an operator, and type the value.

There are two things you can match on:

- **Email Subject** — the subject line
- **Email Body** — the text of the message itself

Both take the same operators: equals, does not equal, contains, does not contain, starts with, ends with.

You can mix them. **+ CONDITION** requires both to be true, **+ OR** accepts either.

![](https://help.iluminr.io/hs-fs/hubfs/image-png-Sep-03-2026-02-46-41-4456-AM.png?width=670&height=538&name=image-png-Sep-03-2026-02-46-41-4456-AM.png)

#### **Matching on the Subject**

Add **conditions** based on email subject line content:

- Subject line **contains** keywords (e.g., "*Critical Alert")*
  
  *OR*
- Subject line **ends with** a specific term (e.g., Los Angeles*)*

![](https://help.iluminr.io/hs-fs/hubfs/image-png-Sep-03-2026-02-53-59-3887-AM.png?width=670&height=376&name=image-png-Sep-03-2026-02-53-59-3887-AM.png)

#### **Matching on the Body**

Most alerting tools put the useful detail in the message body and leave the subject line generic. A monitoring platform might send every notification under the same subject and only name the affected system three lines down. Matching only on the the subject gets you limited results. Matching on the body gets you the system name.

Body conditions work on plain text emails and HTML emails alike. For an HTML email we pull the readable text out of the formatting first and match against that, so you are matching words rather than markup.

**One thing to watch**. The body is the whole body, footers and signatures and legal disclaimers included. If your keyword also turns up in a standard company footer, every single email will match it. Pick a phrase that only appears in the part of the message you actually care about, and test the automation before you rely on it.

![](https://help.iluminr.io/hs-fs/hubfs/image-png-Sep-03-2026-02-53-29-2831-AM.png?width=670&height=356&name=image-png-Sep-03-2026-02-53-29-2831-AM.png)

#### **Complex and specific rules**

Use logical operators (**AND / OR**) to build complex rules.

![](https://help.iluminr.io/hs-fs/hubfs/image-png-Oct-02-2025-09-23-53-7207-AM.png?width=670&height=203&name=image-png-Oct-02-2025-09-23-53-7207-AM.png)

### ![](https://help.iluminr.io/hs-fs/hubfs/image-png-Sep-03-2026-02-58-39-9734-AM.png?width=670&height=248&name=image-png-Sep-03-2026-02-58-39-9734-AM.png)

If every email from a given sender should start the workflow and there is nothing worth filtering on, you can skip conditions altogether. See [***Run an Automation without conditions***](https://help.iluminr.io/knowledge/automation-without-conditions?hsLang=en)

### 4. Defining Actions

Once conditions are met, specify the actions:

- **Notify Contacts**: Alert predefined individuals or groups.
  
    - Learn more about Communication types at: [Get to know Communications](https://help.iluminr.io/knowledge/sending-communications?hsLang=en)
- **Activate Teams**: Initiate response teams with automated messages (e.g., *test automation notification – please commence response)*
- **Broadcast Communications**: Deliver messages via SMS, Email or integrated platforms such as Microsoft Teams.

![](https://help.iluminr.io/hs-fs/hubfs/image-png-Sep-03-2026-03-00-18-6064-AM.png?width=670&height=161&name=image-png-Sep-03-2026-03-00-18-6064-AM.png)

![](https://help.iluminr.io/hs-fs/hubfs/image-png-Oct-02-2025-09-26-15-2951-AM.png?width=450&height=363&name=image-png-Oct-02-2025-09-26-15-2951-AM.png)

![](https://help.iluminr.io/hs-fs/hubfs/image-png-Sep-03-2026-02-59-52-2377-AM.png?width=670&height=438&name=image-png-Sep-03-2026-02-59-52-2377-AM.png)

### 5. Reviewing & Saving

- Preview your configured flow.
- Click **Save** to activate the automation.
- The system will now run the workflow automatically whenever defined triggers and conditions are met.

---

#### Example Use Case

- **Scenario**: An organization wants to ensure immediate escalation of cyber incidents.
- **Configuration**:
  
    - Trigger: Any email sent to *security-alerts@company.com*
    - Condition: Subject line contains *Critical Alert*.
    - Actions: Notify the Security Response Team, activate the Cyber Incident Response Team, and send a broadcast message to leadership.
- **Outcome**: As soon as a qualifying alert email is received, all relevant stakeholders are engaged without manual intervention.

---

 

**Need more assistance? **[Submit a support ticket](http://iluminr.io/resource-centre/support-ticket/?hsLang=en)

 

- [iluminr for Response and Communications](https://help.iluminr.io/knowledge/iluminr-for-response-and-communications?hsLang=en#main-content)

    - [Get Started with Using iluminr](https://help.iluminr.io/knowledge/iluminr-for-response-and-communications?hsLang=en#get-started-with-using-iluminr)
    - [Communications](https://help.iluminr.io/knowledge/iluminr-for-response-and-communications?hsLang=en#communications)
    - [Critical Event Management](https://help.iluminr.io/knowledge/iluminr-for-response-and-communications?hsLang=en#critical-event-management)
    - [Training Options](https://help.iluminr.io/knowledge/iluminr-for-response-and-communications?hsLang=en#training-options)
- [iluminr for Admin Users](https://help.iluminr.io/knowledge/iluminr-for-admin-users?hsLang=en#main-content)

    - [Get started with managing iluminr](https://help.iluminr.io/knowledge/iluminr-for-admin-users?hsLang=en#get-started-with-managing-iluminr)
    - [Integrations](https://help.iluminr.io/knowledge/iluminr-for-admin-users?hsLang=en#integrations)
    - [People and Permission Management](https://help.iluminr.io/knowledge/iluminr-for-admin-users?hsLang=en#people-and-permission-management)
    - [Event Room Management](https://help.iluminr.io/knowledge/iluminr-for-admin-users?hsLang=en#event-room-management)
    - [Alert Automations](https://help.iluminr.io/knowledge/iluminr-for-admin-users?hsLang=en#alert-automations)
- [Troubleshooting](https://help.iluminr.io/knowledge/troubleshooting?hsLang=en)
- [Manage Microsimulations](https://help.iluminr.io/knowledge/manage-microsimulations?hsLang=en#main-content)

    - [START HERE](https://help.iluminr.io/knowledge/manage-microsimulations?hsLang=en#start-here)
    - [Multiplayer Content Management](https://help.iluminr.io/knowledge/manage-microsimulations?hsLang=en#multiplayer-content-management)
    - [Single Player Content Management](https://help.iluminr.io/knowledge/manage-microsimulations?hsLang=en#single-player-content-management)
    - [Learnspace for Single Player Microsimulations](https://help.iluminr.io/knowledge/manage-microsimulations?hsLang=en#learnspace-for-single-player-microsimulations)
    - [Deploying Microsimulations](https://help.iluminr.io/knowledge/manage-microsimulations?hsLang=en#deploying-microsimulations)
    - [Microsimulation Insights (reporting)](https://help.iluminr.io/knowledge/manage-microsimulations?hsLang=en#microsimulation-insights-reporting)
- [Participate in Microsimulations](https://help.iluminr.io/knowledge/participate-in-microsimulations?hsLang=en#main-content)

    - [Participate in Single Player Microsimulations](https://help.iluminr.io/knowledge/participate-in-microsimulations?hsLang=en#participate-in-single-player-microsimulations)
    - [Participate in Multiplayer Microsimulations](https://help.iluminr.io/knowledge/participate-in-microsimulations?hsLang=en#participate-in-multiplayer-microsimulations)

[![Chill listening crop-3](https://help.iluminr.io/hs-fs/hubfs/iluminr_logo.png?width=111&height=24&name=iluminr_logo.png "Chill listening crop-3")](https://iluminr.io?hsLang=en)

[iluminr](https://iluminr.io/?hsLang=en) - [Submit a Support Ticket](https://iluminr.io/resource-centre/support-ticket/?hsLang=en) - [Terms of Use](https://iluminr.io/terms-of-use/?hsLang=en) - [Privacy Policy](https://iluminr.io/privacy-policy/?hsLang=en)

<https://www.linkedin.com/company/iluminr/>

Copyright © 2025, iluminr