---
title: "E-mail Messages"
slug: "v110-e-mail-messages-1"
updated: 2026-11-01T19:56:51Z
published: 2026-11-01T19:56:51Z
canonical: "docs.telosalliance.com/v110-e-mail-messages-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt
> Use this file to discover all available pages before exploring further.

# E-mail Messages

Logic Flows can be used to send e-mails when conditions exist in your system that require attention. For example, it is common to send e-mails to the station’s engineers when silence is detected at a transmitter site.

To send e-mails, you must first configure the e-mail host settings under the System navigation section. If you have not configured these settings, please review the Email Settings section of the System chapter.

Once the e-mail host has been configured and test e-mails can be sent successfully, click the **Messaging > Email Messages** link in the Navigation bar. This is where you can create e-mail messages that can be sent when specific actions take place in the system.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/v20-email-list.png?sv=2026-02-06&spr=https&st=2026-11-02T13%3A28%3A27Z&se=2026-11-02T14%3A28%3A27Z&sr=c&sp=r&sig=Tb3H1TGwyVYqbXRDiAx7uKeQTnWn9aDJK8M8Om6OVEU%3D)

| Column | Notes |
| --- | --- |
| MessageName | The unique **name** of the e-mail message. |
| SendTo | The SendTo **e-mail addresses** to which the message will be sent. |
| Subject | The **Subject** line to be used by the e-mail message. |
| Last Send Date/Time | Displays the last **time** the message was sent. |
| Last Send | Displays information about whether the **last send** attempt was successful or failed. |

Click **edit** to modify the associated e-mail message’s properties. Click the **trash** icon to remove the associated e-mail message. Click **Add +** to add a new e-mail message.

## Adding a New Email Message

- Click **Add +** to create a new email message
- Complete the fields on the Email Message Editor

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/v20-email-editor.png?sv=2026-02-06&spr=https&st=2026-11-02T13%3A28%3A27Z&se=2026-11-02T14%3A28%3A27Z&sr=c&sp=r&sig=Tb3H1TGwyVYqbXRDiAx7uKeQTnWn9aDJK8M8Om6OVEU%3D)

| Field | Notes |
| --- | --- |
| Message Name | Type a **Name** for this email message. This name will be used when this message is accessed via Logic Flows or the API. |
| Recipient Email Address(s) | Type a comma-delineated list of **e-mail addresses** to which this message will be sent. |
| Subject | Type a **Subject** line for generated emails. |
| Auto send on body change | When **checked**, you have the option to define new body content in your e-mail via a Logic Flow, and have it send automatically without having to set the **Send** property. |
| Body | Type the **text** of the e-mail message. You can embed the date and time the message was sent into the subject or body of the email using the variable **<%DateTime%>**. In the example above, when the email is created, the Subject line would include the current date and time like this: *Air chain silent - 2026-10-06T21:15:41.033-04:00* While the Body of the message would look like this: *Silence detected on the air chain at 2026-10-06T21:15:41.033-04:00.* |

- When all fields are complete, click **Apply** to save your changes

## Using E-mail Messages in Logic Flows

Once created, e-mail messages become available for use in Logic Flows. In the following example, we will send the *AudioFailure* email message whenever AirChain’s *AlarmState* becomes *Silent*. We accomplish this by setting the write-only property *Send* to the value *True*.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/v20-email-flow.png?sv=2026-02-06&spr=https&st=2026-11-02T13%3A28%3A27Z&se=2026-11-02T14%3A28%3A27Z&sr=c&sp=r&sig=Tb3H1TGwyVYqbXRDiAx7uKeQTnWn9aDJK8M8Om6OVEU%3D)

You can also change the body of the e-mail message as a Logic Flow end point. This becomes especially useful if you have several conditions that could cause an e-mail alert. For example, we could create a generic e-mail message making sure that the *Auto send on body change* checkbox is engaged.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/v20-email-autosend.png?sv=2026-02-06&spr=https&st=2026-11-02T13%3A28%3A27Z&se=2026-11-02T14%3A28%3A27Z&sr=c&sp=r&sig=Tb3H1TGwyVYqbXRDiAx7uKeQTnWn9aDJK8M8Om6OVEU%3D)

Then we could create multiple Logic Flows, each of which alters the body of the message depending on the start point. For example:

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/v20-email-body-flows.png?sv=2026-02-06&spr=https&st=2026-11-02T13%3A28%3A27Z&se=2026-11-02T14%3A28%3A27Z&sr=c&sp=r&sig=Tb3H1TGwyVYqbXRDiAx7uKeQTnWn9aDJK8M8Om6OVEU%3D)

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/v20-email-body-rules.png?sv=2026-02-06&spr=https&st=2026-11-02T13%3A28%3A27Z&se=2026-11-02T14%3A28%3A27Z&sr=c&sp=r&sig=Tb3H1TGwyVYqbXRDiAx7uKeQTnWn9aDJK8M8Om6OVEU%3D)

Here we use two Logic Flows to send four different messages to the same e-mail recipients.

First Flow

- If “AirChain” is Silent → Set the body of the “AudioStatus” message to be “AirChain silent.”
- If “AirChain” has audio → Set the body of the “AudioStatus” message to be “AirChain OK.”

Second Flow

- If “StudioMonitor” is Silent → Set the body of the “AudioStatus” message to be “Studio monitor silent.”
- If “StudioMonitor” has audio → Set the body of the “AudioStatus” message to be “Studio monitor OK.”

Since we engaged the option to send the e-mail each time the body property of the e-mail changes, this is all that we need to do to handle four alarm conditions using one defined e-mail message.