In this article
You can use this Snap to configure and send emails to the specified email address.
The Send Email is a Write-type Snap.
Valid Exchange Online tenant.
Valid OAuth2 application in Azure Active Directory with all the required API permissions.
Works in Ultra Pipelines. However, we recommend that you do NOT use this Snap in an Ultra Pipeline. To know the list of Snaps that work in Ultra and the related caveats, see Snap Support for Ultra Pipelines.
The size of the attachment has a limitation of supporting file size of 35MB.
For file attachment, the supported protocols are SLDB or Local files.
The Send Email Snap configured with more than 3MB attachment might fail because of a 429 error response from the Graph API endpoint.
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
Input | Document |
|
| Requires the Email Body Type and the Email Content deliver the message. |
Output | Document
|
|
| The output would be a confirmation that the email was sent successfully. |
Error | Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:
Learn more about Error handling in Pipelines. | |||
|
Field Name | Field Type | Description | |
|---|---|---|---|
Label* Default Value: Send Email | String | Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipeline. | |
User/Shared MailBox Default Value: N/A | String/Expression | Specify the mailbox from which you want to send the email. Alternatively, click the Suggestion RecommendationIf you do not provide a user/shared mailbox, the mailbox associated with the user account of the OAuth2 User account (signed in user) is considered. However, if you use an OAuth2 Application account, you must select a User/Shared Mailbox to send emails. RecommendationIf you do not provide a user/shared mailbox, the mailbox associated with the user account of the OAuth2 User account (signed in user) is considered. However, if you use an OAuth2 Application account, you must select a User/Shared Mailbox to send emails. | |
Reply In A Thread Default Value: Deselected | Checkbox | Select to respond to an email under a thread carrying previous emails. On Selecting this option, you will see a new field following, Existing Message Id. On Selecting this option, you will see a new field following, Existing Message Id. | |
Existing Message ID Default Value: N/A | String/Expression | Specify the ID of an existing message which will allow you to respond to an existing email. This field is enabled only if you opt to select Reply In A Thread. This field is enabled only if you opt to select Reply In A Thread. | |
To Default Value: N/A | String/Expression | Specify the recipient's email address. | |
Cc Default Value: N/A | String/Expression | Specify the carbon copy email address. When you Cc people on an email, the Cc list is visible to all other recipients. When you Cc people on an email, the Cc list is visible to all other recipients. | |
Bcc Default Value: N/A | String/Expression | Specify the blind carbon copy address. Unlike with Cc, no one but the sender can see the list of Bcc recipients. Unlike with Cc, no one but the sender can see the list of Bcc recipients. | |
Subject Default Value: N/A | String/Expression | Specify the subject of the email. | |
Email Body Type* Default Value: TEXT | Dropdown list | Select the email body type from the dropdown list:
| |
Email Body Default Value: N/A | String/Expression | Specify the content you want to send in your email. This field supports both HTML and Plaintext format, however, you need to enter the content on the basis of your selection in Email Body Type field. | |
Set Message Importance* Default Value: NORMAL | Dropdown list | Select one of the options to set the priority for your emails:
| |
Email Attachment | Use this fieldset to send an attachment along with your message. | ||
URL Default Value: N/A | String/Expression | Specify the URL of the file to be sent as an attachment along with your email. | |
Table Data Path
Default Value: N/A | String | Specify the JSON path to map the data which corresponds to a row in the HTML table. If it references an array of map data, such as When you use"$" in this field, the Snap creates an HTML table, wherein the Template Body has the HTML table tags ( When you use"$" in this field, the Snap creates an HTML table, wherein the Template Body has the HTML table tags ( | |
Batch size Default Value: 100 | Integer | Specify the batch size to use only for the HTML TABLE Email Body Type. The unit of the value is in the number of rows of the HTML table. If the number of documents the Snap receives from the input view reaches the specified batch size, the Snap composes an email message with an HTML table and sends it to the server. Multiple emails are generated, if needed, to send out all documents. The Snap sends the last message at the end of the Pipeline execution if any unsent table rows remain. | |
Number Of Retries
Default Value: 0 | Integer/Expression | Specify the maximum number of attempts to be made to receive a response. The request is terminated if the attempts do not result in a response. | |
Retry Intervals (seconds)
Default Value: 1 | Integer/Expression | Specify the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception. | |
Snap Execution Default Value: Validate & Execute | Dropdown list | Select one of the three following modes in which the Snap executes:
| |
Error | Reason | Resolution |
|---|---|---|
Message ID is required field for sending an email in thread | You have either not entered a message ID or provided an invalid one. | Enter the Existing Message ID also ensure it to be a valid one. |
Check whether the file path is correct. | You have entered an invalid/incorrect URL for the email’s attachment. | Verify and enter a valid URL for attachments. |
Chunk Upload interrupted | The Snap could not upload the attachments. | Avoid multiple uploading of attachments and retry the process. |
Table Data path is not found. | The Snap could not find a JSON path for the table data. | Provide a valid path for the Table Data. |
The Table Data Path field does not reference a map or an array of maps. | The Snap is unable to map the Table Data path to the HTML table row data. | Please verify if the Table Data Path references a map or an array of maps |
The example below demonstrates how to configure the Exchange Online OAuth2 User Account to send an email using the Send Email Snap.
Prerequisite: Assign Mail.Send permission to the specific user in the registered application in the Azure portal.
Configure the Exchange Online OAuth2 User Account with the Mail.Send permission for Authentication parameter value to allow the user to send emails.
When you click the User/Shared MailBox suggestion in the Send Email Snap settings, the field populates a single email ID, which means that only one user shares the mailbox.
The example below demonstrates how to configure the Exchange Online OAuth2 Application Account to send an email using the Send Email Snap.
The Exchange Online OAuth2 Application Account, by default, has all the permissions provided by Microsoft.
When you click on the User/Shared MailBox suggestions in the Snap settings, the field populates all the users of the mailbox as shown below:
This example Pipeline demonstrates how to send an email to another individual's mailbox.
First, configure the Send Email Snap as follows and validate it.
Send Email Snap Configuration | Output |
|---|---|
 |  |
Upon execution, we see a confirmation that the email has been sent.
Important Steps to Successfully Reuse Pipelines
|
): Indicates a list that is dynamically populated based on the configuration.
icon to select the email folder in the mailbox. For example,