> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/guides/integrating-with-tools/messanger-apps/email.md).

# Email

BugSplat’s integration with Email Alerts allows your team to receive every new crash from a specific database as an alert or know when a new type of crash has occurred in a database.

These alerts let you stay on top of your crashes and can serve as an early warning that something might be wrong.

#### Integrating Email Alerts with BugSplat <a href="#integrating-email-alerts-with-bugsplat-docs" id="integrating-email-alerts-with-bugsplat-docs"></a>

1. Login to your [account](https://app.bugsplat.com/cognito/login).
2. Go to the [Notifications](https://app.bugsplat.com/v2/database/integrations#notifications) page.
3. To receive emails when your database's crash rate exceeds a certain level, fill in the **Email** and **Reports (per minute)** fields under **Crash Rate Alerts** and click **Update**.
4. To receive hourly summaries of your database's crash activity, fill in the **Email** field under the **Hourly Report Digest Email** section and click **Update**.


---

# 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.bugsplat.com/guides/integrating-with-tools/messanger-apps/email.md?ask=<question>&goal=<user_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.