> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/integrations/integration-fundamentals/messaging-and-ticketing-integrations/email-notifications.md).

# Email Notifications

## Overview

Email notifications are useful for proactive notifications so your team can focus on other priorities until something requires attention, especially for critical issues that need immediate attention. You can configure them to trigger based on multiple events and customize the body.

<figure><img src="/files/pGH4fUPLe0pBLuyaungi" alt=""><figcaption></figcaption></figure>

## Create an email notification

1. In Material, click **Integrations** (the puzzle icon in the top tool bar).
2. Click **Create New Integration**
3. Scroll to **Messaging & Ticketing**, then click **Email**. Complete the required fields:

<figure><img src="/files/rcoeYL48fbFe731YCNWN" alt=""><figcaption></figcaption></figure>

**In the Event Workflow:**

4. Set the **IF** parameter to `Issue Change` . (Most event subscriptions use `Issue Change` or `Issue Update`). Learn more about events [here](/integrations/integration-fundamentals/messaging-and-ticketing-integrations.md#event).
5. Filter to refine the email trigger. Common filters are `Severities` or specific `Detections` .

**In the Email:**

<figure><img src="/files/fGCDiJYwzwlHB1Ne6MHW" alt="" width="375"><figcaption></figcaption></figure>

6. **To:** Enter one or more recipient email addresses, comma separated.
7. **Subject:** you can include standard text and/or use the subject drop-down to also include a variable(s) like the time or message ID. You can include multiple variables (just use the drop-down to add them one at a time):

   <figure><img src="/files/Pr7mYuNUlNe5Hcom2UGv" alt="" width="319"><figcaption></figcaption></figure>
8. Build the email **body** with text and variables from the **Body** drop down. You can include multiple variables (just use the drop-down to add them one at a time):

   <figure><img src="/files/X9MTa8rfxXgTsFVbj0bK" alt="" width="375"><figcaption></figcaption></figure>
9. Save, then click **Send Test Event**. You should see something like this in the inbox you chose:

   <figure><img src="/files/vMnxba7gRwp7m6iC6tyJ" alt=""><figcaption></figcaption></figure>

***

## Recipes

* [User Clicks through a speedbump](#create-an-email-notification)

***

## Resources

Review [Messaging and Ticketing integrations](/integrations/integration-fundamentals/messaging-and-ticketing-integrations.md) for more detail about events and troubleshooting.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.material.security/integrations/integration-fundamentals/messaging-and-ticketing-integrations/email-notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.