Outlook Send Email
The Outlook Send Email component connects to a Microsoft Outlook service account mailbox and sends email messages to one or more recipients, including configurable details such as recipients, subject, body content, attachments, and email priority. It is commonly used for automated notifications, alerts, and communications.
Prerequisites
- Valid Microsoft Outlook/Microsoft 365 credentials.
- The configured mailbox must have permission to send emails.
- For Reply, Reply All, and Forward actions, a valid Message ID is required. The Message ID can be obtained from the output JSON of the Outlook Read Email component.
Authentication
| Field | Description |
|---|---|
| Username* | Specifies the Outlook/Microsoft 365 mailbox used to perform the email action (for example, a service account mailbox). Enter the email address of the mailbox to use. |
| Action* | Select the email operation to perform: Send, Reply, Reply All, or Forward. |
Action Values
| Value | Description |
|---|---|
| Send | Sends a new email to the specified recipients. |
| Reply | Sends a reply to the original sender of an email. |
| Reply All | Sends a reply to the original sender and all recipients included in the To and CC fields. |
| Forward | Forwards an existing email to one or more recipients. |
Note: To use Reply, Reply All, or Forward, provide a Message ID generated by a previous Outlook Read Emails action.
Email Fields
| Field | Description |
|---|---|
| Subject | Specifies the subject line of the email. Supports dynamic values and full-screen editing. |
| Email Body* | Specifies the content of the email. Supports HTML formatting when Is HTML Body is enabled. |
| To Recipients | Specifies one or more primary recipient email addresses. |
| CC Recipients | Specifies one or more carbon copy (CC) recipient email addresses. |
| BCC Recipients | Specifies one or more blind carbon copy (BCC) recipient email addresses. These recipients are hidden from other recipients. |
| Attachment Paths | Specifies one or more local or network file paths to include as email attachments. To attach multiple files, provide the file paths as a comma-separated list. |
| Attachment Input | Connects the node to accept file data from a previous workflow step, such as a generated document, report, or other file output, and includes it as an email attachment. |
| Message ID | Specifies the unique identifier of the email being replied to or forwarded. Required for Reply, Reply All, and Forward actions. |
Note: To preserve formatting, provide the email body in HTML and enable Is HTML Body. Otherwise, the email will be sent as plain text, and HTML tags will be displayed as plain text.
Execution Options
| Parameter | Description |
|---|---|
| Is HTML Body | When enabled, the email body is sent as HTML, preserving formatting such as fonts, colors, tables, hyperlinks, and text styling. When disabled, the email is sent as plain text. |
| Save to Sent Items | Saves a copy of the sent email in the mailbox's Sent Items folder. |
| Timeout (Seconds) | Specifies the maximum time to wait for the action to complete before it is marked as failed. Default: 30 seconds. |
| Retry Count | Specifies the number of retry attempts if the action fails. Default: 1. |
| Delay Between Retries (Seconds) | Specifies the wait time between retry attempts. Default: 1 second. |
| Delay Before Execution (Seconds) | Specifies the delay before the action begins execution. Default: 0 seconds. |
| Delay After Execution (Seconds) | Specifies the delay after the action is completed before the workflow continues. Default: 0 seconds. |
| Continue on Error |
Defines the workflow behavior when the action fails:
|
Result
Upon completion, the action returns the execution status.
| Status | Description |
|---|---|
| Success | The email operation was completed successfully. |
| Failure | The email operation failed. Refer to the workflow logs or error details to determine the cause. |
Notes
- Fields marked with an asterisk (*) are mandatory.
- HTML formatting is applied only when Is HTML Body is enabled.
- Multiple recipients can be specified in the To, CC, and BCC fields.
- Attachments can be provided using file paths or outputs from previous workflow actions.
- A valid Message ID is required only for Reply, Reply All, and Forward operations.
