Send Email
Send Email delivers HTML notifications through a configured email server, can batch several events into one message, and can attach created files when the forwarded event contains a file reference.
Send event-driven email alerts and digests
Use Send Email when Event Manager rules, manual actions, schedules, or action groups should notify operators by email. The action renders the current event through an HTML template, sends it through the selected email server, and optionally batches several events into one message.
Before wiring the action into production rules, configure and test the email server connector, then run a manual smoke test with the final recipients, subject, template, and attachment behavior.
Select the email server
Choose E-Mail server that already has working SMTP settings. A successful action trigger means the email was queued for sending, not necessarily accepted by the remote SMTP server.
Set recipients and subject
Fill To (comma delimiter) and Subject. Use Cc (comma delimiter) and Bcc (comma delimiter) for additional recipients or private distribution lists.
Choose immediate or batched delivery
Keep Message batch size at 1 for immediate alerts. Increase it and configure Message batch timeout when noisy events should be grouped into a digest.
Configuration parameters
| Parameter | Required | Description | Default |
|---|---|---|---|
Title | Yes | Display name of the action. Use a name that identifies the alert purpose, for example camera offline email, motion digest, or storage warning. | None |
E-Mail server | Yes | Email server connector used to send messages. Configure and test SMTP settings before relying on production alerts. | None |
From | Optional | Sender address or addresses. Leave empty when the sender configured in the email server should be used. Set it only when the SMTP server allows that sender address. | Email server default |
To (comma delimiter) | Yes | Primary recipient addresses separated by commas. | None |
Cc (comma delimiter) | Optional | Carbon-copy recipient addresses separated by commas. | Empty |
Bcc (comma delimiter) | Optional | Blind-copy recipient addresses separated by commas. Use it for private distribution lists where recipients should not see each other. | Empty |
Subject | Yes | Email subject. The subject is sent as configured; template variables are applied to Template, not to the subject. | None |
Template | Yes | HTML body template. Supported variables are , , and . Use HTML tags such as <br> when line breaks must be visible in email clients. | : <br><hr> |
Message batch size | Yes | Number of events to collect before sending one email. Use 1 for immediate delivery. Valid range: 1-100. | 1 |
Message batch timeout | Optional | Maximum wait time in seconds before a partial batch is sent. Enabled when Message batch size is greater than 1. Valid range: 1-60. | 1 |
Render an event into HTML email
When triggered by an event, the action renders the event with Template, queues an HTML email through the selected email server, and optionally attaches the related file when the event describes a newly created recording, snapshot, or file.
When run manually or by schedule, the action creates a simple manual or scheduled status message and sends it through the same template. This is useful for smoke tests and scheduled status emails.
Email connector
The selected email server owns SMTP connectivity, authentication, TLS settings, and asynchronous send behavior.
HTML template
The template turns the current event, event index, and attachment error text into an HTML body.
Batching
Batching reduces email noise by grouping event bursts into one message before the size or timeout threshold is reached.
Choose email behavior for alert urgency and volume
Immediate email alert
Set Message batch size to 1 when each event should produce its own email immediately. This is best for rare and important events such as camera offline, disk nearly full, intrusion alarm, or manual emergency action.
Batched event digest
Set Message batch size above 1 and configure Message batch timeout when many events may fire in a short time. This reduces email noise for motion bursts, repeated status changes, or file creation sequences.
File notification
Use this action after recording or snapshot tasks that create files. The action tries to resolve the created file through its storage and attach it to the email.
HTML message layout
Use HTML tags in Template, for example <b></b><br><hr>. The body is sent as HTML, so visible line breaks should be written as <br>.
Multi-recipient notification
Put comma-separated addresses into To (comma delimiter), Cc (comma delimiter), and Bcc (comma delimiter). Use Bcc for private distribution lists.
Connector-default sender
Leave From empty when the SMTP account configured in the email server should be used as the sender. Set From only when the SMTP server allows that sender address.
Manual or scheduled report
When the action is run manually or by schedule, it creates a manual or scheduled status message and sends that through the same template. This is useful for smoke tests and simple scheduled status emails.
Event summary with attachment errors
Include in the template when file attachment is expected. If the action cannot resolve a file, the error text is inserted into the rendered message.
Operational notes
Template variables are limited
Supported template variables are , , and . The index is the zero-based position of the event inside the current batch.
Subject is not templated
Subject is sent as configured. The current implementation substitutes variables only in Template, not in the subject.
Batches flush by size or timeout
For Message batch size above 1, the action sends mail when the batch reaches the configured size or when the periodic timeout flush runs.
Queued does not mean delivered
The underlying email connector sends messages asynchronously using a small send pool. A successful action trigger means the email was queued for sending, not necessarily accepted by the remote SMTP server.
Keep attachments small
Large attachments can slow SMTP delivery, exceed provider limits, or overload recipients. Keep snapshot and video notifications small or use links and paths in the template when files are large.
Connector must be healthy
If the email connector is stopped, removed, or misconfigured, the action cannot send mail. Test SMTP settings with a manual run before relying on production alerts.
Avoid mail storms
Avoid sending high-frequency raw detector events directly to email without batching or filtering. Prefer Event Manager rules, cooldowns, and batch settings to avoid notification storms.
Use as a terminal action
The action stops downstream task processing after handling an event, so use it as a terminal action in a task chain unless stopping downstream tasks is intentional.