# Email Integration
Route alerts into Squadcast using Email endpoints of Services from platforms that support Email integrations.
### In Squadcast: Using Email as an Alert Source
1. Navigate to **Services** -> **Service Overview** -> select or search for your Service. Expand the accordion -> In the Alert Sources section, click **Add**.
2\. Select **Email**. Copy the displayed **Webhook URL** to [configure](#how-to-configure-the-email-prefix-for-a-new-service) it within **Email**. Finish by clicking **Add Alert Source** -> **Done**.
{% hint style="warning" %}
**Important:**
When an alert source turns Active, it’ll show up under Configured Alert Sources, you can either generate a test alert from the integration or wait for a real-time alert to be generated by the Alert Source. An Alert Source is active if there is a recorded incident via that Alert Source for the Service.
{% endhint %}
### In the external platform which you are using: Configure the Email endpoint
Head over to the platform from where you want to route alerts into Squadcast. Navigate to the section where you can *configure the Email endpoint/integration*. Then, paste the copied Email address in the right placeholder and test this integration, if there is a provision to do so, and validate that the integration works.
That's it, your Email integration is now good to go!
{% hint style="info" %}
**Note**
* The Incident Message will be the subject of the Email and the Incident Description will contain the body of the Email
* Each email alert source is associated with a single, unique email endpoint. Emails can only be sent to one endpoint address at a time.
{% endhint %}
### How-to: Configure the Email Prefix for a new Service
**(1)** On the **Sidebar**, click on **Services**
**(2)** Select **Add service**
**(3)** Add the details in the box as required along with configuring the **Email Prefix**
**(4)** Click on **Save** to create the new Service with an Email Prefix of your choice
### How-to: Rename the Email Prefix for an existing Service
**(1)** On the **Sidebar**, click on **Services**
**(2)** For the Service for which you want to rename the Email prefix, click on the **Edit** option
**(3)** Select **Edit** in the drop-down
**(4)** Replace the existing prefix with the prefix of your choice in the placeholder for **Email Prefix**
**(5)** Click on **Save**
Now, whenever an Email is sent to the Service's Email address, Squadcast will trigger an incident for it.
{% hint style="info" %}
**Note**
This integration does not support **auto-resolution** of incidents. If the platform you are using resolves an alert, you will have to manually resolve the corresponding incident in Squadcast via the [web app](https://www.app.squadcast.com) or the [Squadcast mobile app](https://support.squadcast.com/mobile-app/using-the-mobile-app).
{% endhint %}
{% hint style="warning" %}
**Important**
* If you are sending regular emails - emails in the `text/html` format, URLs for images will appear as URLs only. If the image is added inline, only the name of the file will appear and not the image. However, please note that if the image is added as an attachment, it will not show up in the payload (and hence, the Incident Description).
* If you are sending emails as plain text - emails in the `text/plain` format, you can add images using the Markdown syntax ``. The link of the image will appear in the Incident Description. Similarly, you will also be able to format the body content using Markdown, and the content with the same formatting will be displayed in the Incident Description.
{% endhint %}
*Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*
---
# Agent Instructions: 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:
```
GET https://support.squadcast.com/integrations/alert-source-integrations-native/email.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.