A notification is a custom Craft element that stores:
Notifications can be duplicated, disabled, deleted, and restored through Craft's element index actions.
Each notification listens to one event. Super Mailer discovers supported event constants and lists content-related events in the event picker.
Examples:
Events are normalized into a serializable context before being pushed to the queue. This keeps queue payloads safe while still letting templates work with useful objects later.
In templates, you can use:
{{ event.element.title }}
{{ event.getElement().title }}
{{ event.eventName }}
{{ rawEventContext|json_encode }}rawEventContext is the stored queue payload. event is the template-facing render context. The selected notification event determines which values are available, so use the preview page's Template Variables panel as the source of truth for a specific notification.
Conditions run before queueing. A notification queues only when its condition rows and PHP condition pass.
Condition rows are generated from the selected event. Super Mailer shows practical filters for the event's element type, such as status, site, Entry section/type/author, category group, custom field layout values, submission form/status/user, and Commerce product/store/order filters when available.
Option-style fields use their configured options, and multi-value rows support both contains and does not contain. Toggle fields use a switch without a separate comparison selector.
Condition rows can be reordered for readability and can match all rules or any rule.
When conditions pass, Super Mailer pushes a SendNotificationEmailJob to Craft's queue. The queue job renders recipients, subject, and templates, sends the message, and records a log.
Every send attempt records:
Logs can be inspected, deleted, bulk deleted, resent, and automatically purged by retention settings.