> 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.
## Create an email notification
1. In Material, click **Integrations** (the puzzle icon in the top toolbar).
2. Click **Create New Integration**
3. Scroll to **Messaging & Ticketing**, then click **Email**. Complete the required fields:
**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:**
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):
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):
9. Save, then click **Send Test Event**. You should see something like this in the inbox you chose:
***
## 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.material.security/integrations/integration-fundamentals/messaging-and-ticketing-integrations/email-notifications.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
