Skip to main content
Version: Current

Send Template Email

Description​

The Send Template Email activity sends an email message via SMTP, either using the global SMTP configuration defined in the AI Command Center or a specified SMTP connection.

Common settings​

Use Process Data to bind supported inputs to workflow values or upstream outputs. See Common Activity Features for shared execution, error-handling, and output-persistence settings. Availability depends on the activity.

Design-Time Configuration​

Display Text​

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

Retry Count​

Specifies the maximum number of retry attempts if sending the email fails.

  • Minimum value: 1
  • Default value: 30

The activity retries automatically until the retry count is exhausted or the email is sent successfully.

Execution Control (Wait All Incoming)​

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

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

Error Handling (On Error)​

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

For supported strategies (Fault, Continue, Suspend, Retry), see   On Error Handler.

Use Global SMTP Configuration​

Determines whether the activity uses the global SMTP configuration defined in the AI Command Center.

  • Enabled (default)   Uses the globally configured SMTP settings.
  • Disabled   Requires an explicit SMTP connection to be selected in Connection Name.

Connection Name​

Specifies the SMTP connection to use when Use Global SMTP Configuration is disabled.

This field is ignored when the global SMTP configuration is enabled.

Email Template​

Specifies the email template used to compose the message.

  • Select an existing template from the dropdown
  • Click + to create a new email template
  • A preview of the selected template is displayed

The template defines recipients, the subject, the body, the format (HTML or text), and attachments.

Output​

This template-based activity does not expose a Message ID output. It completes after the email delivery service reports a successful send; a reported send failure is handled through On Error.

Notes​

  • The selected email template must include a valid To address.   If the To field is empty, the activity fails.
  • HTML or plain text emails are supported based on the template configuration.
  • Attachments can be added from the file system.
  • Potentially dangerous file extensions (for example, .exe, .bat, .js, .vbs) are blocked for security reasons.
  • Template fields support variable parsing using process data syntax   (for example: {{ Model.CustomerEmail }}).
  • If sending fails, the activity retries automatically based on the configured Retry Count.

Example: Send a processing notification​

  1. Create an Email Template with a valid To, subject, and HTML or plain-text body. Insert business values through the template's data-binding controls.
  2. Add the template-based send activity and select that template.
  3. Enable Use Global SMTP Configuration, or disable it and select Connection Name for a tested SMTP connection.
  4. Set Retry Count for the email delivery attempts. This is separate from workflow-level On Error → Retry, which can repeat the activity.
  5. Run with a test recipient and verify the resolved recipient, subject, body, and attachments.

For attachments, bind file outputs supported by the template editor. Keep To populated after expression evaluation; a blank recipient causes an error.

Help improve this page