Introduction
Send a single daily summary email covering every device that ran through this step in the past 24 hours. Instead of getting one email per device, you get one consolidated report — a shared body with a per-device detail section built from whatever data you want to capture.
Use this action for regular visibility into fleet state: encryption status, patch compliance, software inventory, or any other condition you're tracking across devices.
Send Email Report Action
From the automation pipeline in edit mode, click + and select Send email report from the Notifications category.
Email(s)
One or more recipient email addresses. Required. Press Tab or type a comma to add additional addresses.
Subject
The email subject line. Required. Click (x) to insert a variable reference.
Example: Daily Encryption Status Report — {{level_time}}
Body
The email body — content that appears once, above the per-device rows. Use this for context, instructions, or a header for the report.
Example:
Daily encryption status report for all managed devices. Devices without encryption enabled require immediate attention.
Per-device details
A template for each device's row in the report. This section repeats once per device.
Click (x) to insert variables — automation variables from earlier steps in the pipeline are available here, along with system variables and custom fields.
Example:
{{level_device_hostname}} — {{bitlocker_status}}The resulting email lists every device that ran through this step in the past 24 hours, with one row per device using the template you defined.
💡 TIP: Pair Send Email Report with earlier pipeline steps that capture device state into automation variables. For example: run a script that checks BitLocker status and sets a bitlocker_status variable, then use that variable in the Per-device details field to get a row like DESKTOP-01 — Encrypted or LAPTOP-22 — Not encrypted for every device in the run.
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.
ℹ️ NOTE: A common pattern is to use an Action Condition on this step to filter which devices appear in the report. For example, set a condition where bitlocker_status equals Not encrypted — only devices without encryption will generate a row in the report.
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
When does the report send? Once per day at 8:00 PM UTC. The report covers all devices that passed through the step in the prior 24 hours (8:00 PM UTC the previous day through 8:00 PM UTC today).
What if no devices ran through the step in 24 hours? No email is sent — the report is suppressed if there's nothing to report.
Can I have multiple Send Email Report actions in the same automation? Yes — each action is configured independently with its own recipients, subject, body, and per-device template.
Who can add or modify Send Email Report actions? Technicians with permission to edit automations in the relevant group. See Workspace → Permissions for access control configuration.