Skip to main content

Send Email Action

Send an email to one or more addresses as part of an automation pipeline.

Updated this week

Introduction

Send an email to one or more recipients during an automation run. Use this action to notify technicians, clients, or any address when something worth reporting happens β€” a failed update, a completed deployment, a device going offline.

For a scheduled summary email across multiple devices, see Send Email Report instead.


Send Email Action

From the automation pipeline in edit mode, click + and select Send email from the Notifications category.

Send Email Action

Email(s)

One or more recipient email addresses. Required. Press Tab or add a comma to enter additional addresses.

Subject

The email subject line. Required. Click (x) to insert a variable, system variable, or custom field reference.

Example: Update failed on {{level_device_hostname}}

Body

The email body. Required. Click (x) to insert variable references to include device-specific context inline.

Example:

The scheduled Windows update failed on {{level_device_hostname}}. 

Device: {{level_device_hostname}}
Group: {{level_group_name}}
Last seen: {{level_device_last_seen_at}}

Review the automation run history for details.

Conditions

The Conditions section lets you restrict when this action runs based on device attributes or the outcome of a previous action.

See Action Conditions for the full reference on condition types, operators, and values.


Additional Options

Expand Additional options for action name, failure behavior, output variable assignment, retries, and the enabled toggle.

See Actions Overview for the full reference on additional options available on every action.


FAQ

  • Can I send to multiple recipients? Yes β€” press Tab or type a comma after each address to add more.

  • Does the email come from a Level address? Yes β€” emails are sent from Level's email infrastructure, not an email you configure.

  • Who can add or modify Send Email actions? Technicians with permission to edit automations in the relevant group. See Workspace β†’ Permissions for access control configuration.

Did this answer your question?