> For the complete documentation index, see [llms.txt](https://docs.senpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.senpiper.com/alarm-builder/setting-up-an-alarm/add-new-alarm/defining-the-communication-type/send-an-email.md). # Send an Email ## Selecting the communication type For configuring the type of alert, under **Select communication type**, enter/select the values for the following fields:

Field	Description
Select communication type	Select Email as the type of alert that you want to configure
Enter Sender's Name	Enter the name of the sender to be attached to the email The recipient of this email will see this name in the From* field of the email details.*
Enter Sender's Email ID	Enter the email ID of the sender from which the email alert is to be sent The recipient of this email will see this email ID in the From* field of the email details.*
Enter Reply to Email ID	Enter an email ID to which the receiver may reply
Email Subject	Enter a subject for your email notification
Email Body	Enter the text that you want to send in the email

> ### How to add dynamic values to create custom message? > > To fetch and send out dynamic values in message body, just type " \[ " and this will open a list of all the form fields that can be added and used to create a customized message.

*Create custom message by adding dynamic values*

## Selecting the receivers for your email For configuring the receivers of the alert, under **Select receivers**, select the required options from the fields below :

*Select Receivers for An Email Communication*

| Field | Description | | ------------------------------------------------- | ----------------------------------------------------------------------------------------- | | Users who are present in company-defined roles | You must select the roles to which the Email is to be sent. | | Email IDs from a particular field in the form | You must select the Form fields, to the values to which you want to send the email alert. | | Custom email ID list | You must enter the email ID(s) to which you want to send the email alert. | | Cc Users who are present in company-defined roles | You must select the roles to which you can cc the Email | | Cc Email IDs from a particular field in the form | You must select the Form fields, to the values to which you want to Cc the email alert. | | Cc Custom email ID list | You must enter the email ID(s) to which you want to Cc the email alert. | ## Setting a condition for your alerts Now the last stage is where we configure the notification alerts to be sent out based on a predefined condition. Refer to the steps to configure a condition for alerts [**here**](https://docs.senpiper.com/alarm-builder/setting-up-an-alarm/add-new-alarm/defining-the-communication-type/pages/-MhrvLO7WH40juxnOipm#3.-setting-a-condition-for-your-alerts). --- # 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.senpiper.com/alarm-builder/setting-up-an-alarm/add-new-alarm/defining-the-communication-type/send-an-email.md?ask=&goal= ``` `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.