Mailer Before Send is a Trigger in Joomla Events › Mailer Events. Before Joomla sends an email via the mailer (Mail::send).
Mailer Before Send is a Trigger in Joomla Events › Mailer Events. Before Joomla sends an email via the mailer (Mail::send).
Plugins can alter recipients, subject, body, or abort send.
Each run also includes who was logged in at the time and what kind of item was involved — see audit_user and audit_type in Payload Fields below.
This trigger is not connected yet — flows using it will not run until JOrchestrator adds support for this Joomla hook.
When this trigger fires, JOrchestrator starts the flow and passes the incoming event or request data to the next connected step. Configure filtering, payload shape, and security on the Design tab.
Mailer Before Send is a trigger in the Joomla Events › Mailer Events group. Triggers start a flow. They listen for an external signal — a CMS event, inbound HTTP call, payment notification, or schedule — and pass the incoming data to the first downstream step.
Typical reasons teams add Mailer Before Send to a flow:
MailerBeforeSendBefore Joomla sends an email via the mailer (Mail::send).
Common patterns on the canvas:
The designer shows these tabs for this node:
| Tab | Purpose |
|---|---|
| Info | Plain-language description and output payload fields for downstream steps |
| Design | Trigger configuration and payload schema |
These fields are managed by the designer or runtime — you do not type into them directly:
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
_nodeId | Node ID | node-id | No | — | — |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
label | Label | text | No | — | Node label |
Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under Node Configuration, not per step on this node. Link the flow to a domain before testing CMS-backed fields.
After this step runs, later nodes can reference these fields using placeholders such as {{mailer_before_send.mailer}}.
| Field key | Type | Description |
|---|---|---|
mailer | object | Nested object from this node's output. |
to | string | Recipient address or user. |
subject | string | Email or notification subject line. |
body | string | Raw content — response text, file bytes (often base64), or message body. |
cc | array | Array of values from this node's output. |
bcc | array | Array of values from this node's output. |
replyTo | string | Text value from this node's output. |
audit_user.id | number | Nested field "audit_user.id" from this node's output payload. |
audit_user.username | string | Nested field "audit_user.username" from this node's output payload. |
audit_user.email | string | Nested field "audit_user.email" from this node's output payload. |
audit_user.name | string | Nested field "audit_user.name" from this node's output payload. |
audit_user.guest | boolean | Nested field "audit_user.guest" from this node's output payload. |
audit_user.client | string | Nested field "audit_user.client" from this node's output payload. |
audit_type | string | What kind of item triggered the event — for example article, category, or user. |
Other steps in the same area of the palette:
event-onActionLogAfterAdd) — Joomla Events › Action Log Eventsevent-onActionLogBeforeAdd) — Joomla Events › Action Log Eventsevent-onAfterCompileHead) — Joomla Events › After Eventsevent-onAfterDispatch) — Joomla Events › After Eventsevent-onAfterInitialise) — Joomla Events › After Events