Skip to main content
Version: Current

Send Outlook Email

Description

The Send Outlook Email activity sends an email message through Microsoft 365 (Outlook) using the Microsoft Graph API.

This activity uses an Outlook connection configured in the AI Command Center and supports dynamic email content, templates, and attachments.


Common Capabilities

Process Data Support

info

This activity supports dynamic configuration using variables from the Process Data drawer.

You can bind values from:

  • Model Data
  • Form Data
  • System Data
  • Enterprise Variables
  • Activity Outputs

Variables may be used directly or inside Liquid or JavaScript expressions where supported.

Learn more → Using Process Data


Design Time Configuration

Display Text

Specifies the activity's display name as shown on the workflow canvas.

Connection Name

Selects the Outlook (Microsoft 365) connection used to send the email.

Email Template

Specifies the email template used to compose the message.

  • Select an existing template from the drop-down list.
  • Click + to create a new template if required.
  • A preview of the selected template is displayed for validation.

Templates support:

  • Dynamic fields using process data ({{ variable }})
  • HTML and plain text formats
  • Attachments from the file system

Execution Control (Wait All Incoming)

Controls how the activity behaves when multiple incoming execution paths converge.

For detailed behavior and usage guidance, see   Execution Control – Wait All Incoming.

Error Handling (On Error)

Defines how the workflow proceeds if the activity encounters an error.

Supported strategies include Fault, Continue, Suspend, and Retry.

For details, see   On Error Handler.


Output

Message ID

Returns the Microsoft Graph message ID of the sent email, if available.


Notes

  • The selected email template must include a valid To address.   If the To field is empty, the activity fails.
  • If the From address is not specified in the template, the EmailAddress configured in the Outlook connection is used.
  • Both HTML and plain text email bodies are supported, based on the template configuration.
  • Attachments can be added from the file system.   - Potentially dangerous file types (for example, .exe, .bat, .js, .vbs) are blocked for security reasons.
  • Template fields support variable parsing using the process data parser   (for example: {{ OrderId }}, {{ Initiator.Email }}).