Outlook Send Email

Controlled node

Overview

Sends an email via Outlook on behalf of the connected user. This node requires an Outlook connection to be configured in the project settings. It supports sending to multiple recipients via To, CC, and BCC fields, and allows attaching files from the Intellectible library.

The node automatically validates email addresses before sending and supports both plain text and HTML body content. If both bodyText and bodyHtml are provided, the HTML version takes precedence in most email clients.

Connection Requirements

This node requires an active Outlook connection configured in your project. The connection must have permissions to send emails on behalf of the user.

Inputs

Input	Type	Description	Default
Run	Event	Fires when the node starts running	-
To	Text	Primary recipient email address(es). Can be a single email string or an array of email strings.	-
CC	Text	Carbon copy recipient email address(es). Can be a single email string or an array of email strings.	-
BCC	Text	Blind carbon copy recipient email address(es). Can be a single email string or an array of email strings.	-
Subject	Text	The subject line of the email.	-
Body Text	PlainText	The plain text version of the email body.	-
Body HTML	PlainText	The HTML version of the email body. If provided alongside Body Text, most clients will display the HTML version.	-
Attachments	Data	File attachments to include. Accepts a single file object or array of file objects from the Intellectible library (each object must have id and name properties).	-
Connections	Connection	The Outlook connection configuration to use for sending. Configure this in the properties panel.	-

Outputs

Output	Type	Description
Done	Event	Fires when the email has been sent or if sending fails.
Status	Data	Contains the status of the send operation. Returns success confirmation or error details if validation fails or the send operation encounters an error.

Runtime Behavior and Defaults

• Email Validation: The node automatically validates all email addresses (To, CC, BCC) using standard email regex validation before attempting to send. If any email is invalid, the node will output a failure status and not attempt to send.
• Attachment Handling: Attachments must be file objects from the Intellectible library containing at least id and name properties. Single attachments are automatically wrapped into an array.
• Body Content: If both bodyText and bodyHtml are provided, the email will contain both versions, allowing email clients to choose the appropriate format.
• Error Handling: If the Outlook connection is invalid or the send operation fails, the status output will contain the error message and the done event will still fire.
• Rate Limiting: Be aware of Microsoft Graph API rate limits when sending large volumes of emails.

Example Usage

To send an email with attachments:

1. Connect a Start node or any event-emitting node to the Run input.
2. Provide recipient email addresses in the To field (e.g., "user@example.com" or ["user1@example.com", "user2@example.com"]).
3. Enter a Subject and Body Text (or Body HTML for formatted emails).
4. (Optional) Attach files by connecting a Get Library Files node or similar to the Attachments input.
5. Configure the Connections property in the panel UI to select your Outlook connection.
6. Connect the Done output to subsequent nodes to continue the workflow after sending.

Multiple Recipients

When sending to multiple recipients, you can provide an array of email strings to the To, CC, or BCC inputs, or use a single string for individual recipients.