The Output to Email Node allows you to automatically send structured email reports based on workflow outputs. This node is ideal for delivering real-time alerts, scheduled summaries, or targeted data snapshots to users, teams, or custom email address
What It Does
This node captures payload data at a specific point in your workflow and delivers it via email. You can configure the subject, header, body, and footer of the message, define sender information, and determine who should receive the email—either via user groups, manually entered addresses, or dynamic keys from the payload.
It can be used for both event-based alerts (e.g., when thresholds are exceeded) and reporting-style outputs.
Step-by-Step: How to Configure the Output to Email Node
1. Add the node
Drag the Output to Email node onto the canvas.
2. Set the node name
Give your node a clear identifier (e.g., "Send Alert Email").
3. Enable event-based reporting (optional)
If this node is meant to send emails only when triggered by a specific event or rule node, enable Enable for event-based report.
4. Fill in email fields
-
Subject: The email subject line. You can use payload values like
Alert: exceeded threshold. -
Header: (Optional) Text shown at the top of the email body.
-
Body: Main message. You can use plain text, JSON formatting, or interpolated values.
-
Footer: (Optional) Message footer (e.g., contact info or disclaimer).
5. Configure sender details
-
Sender: Email address from which the email will be sent.
-
Sender Name: Friendly display name (e.g., "Rayven System Monitor").
6. Define recipients
Choose one or more of the following:
-
Configure recipients in User Group: Select a predefined Rayven user group to receive the email.
-
Send to email (without creating user): Enter external email addresses (comma-separated).
-
JSON key with emails: If email addresses are part of the payload, specify the JSON key (e.g.,
payload.alert_emails) for dynamic delivery.
Configuration Fields
| Field | Requirement | Description |
|---|---|---|
| Node Name* | Required | Name shown in the workflow canvas. |
| Enable for event-based report | Optional | Restrict node execution to only event-triggered payloads. |
| Subject* | Required | Email subject line. Can include dynamic variables. |
| Header | Optional | Text shown above the main body. |
| Body* | Required | Core message content. Supports text and variable injection. |
| Footer | Optional | Footer message (e.g., signatures, links, notes). |
| Sender | Optional | Email address from which the message is sent. |
| Sender Name | Optional | Display name shown as the sender. |
| Configure recipients in User Group | Optional | Send to all users in selected Rayven group. |
| Send to email (without creating user) | Optional | Directly input external addresses (comma-separated). |
| JSON key with emails | Optional | Key pointing to dynamic email list in payload. |
Example: Alert Email for High Temperature
Payload Input:
{
"device_id": "sensor_001",
"temperature": 72.3,
"alert_emails": ["ops@example.com", "maintenance@example.com"]
}
Configuration:
-
Subject:
High Temp Alert – -
Header:
A temperature threshold has been exceeded. -
Body:
Device:
Temperature: °C
Timestamp: -
Footer:
Please check the system and take appropriate action. -
Sender:
noreply@rayven.io -
Sender Name:
Rayven Alert System -
JSON key with emails:
alert_emails
Result:
An email is sent to both addresses in the payload, with dynamic values injected into the message.
Best Practices
-
Use JSON keys for emails when routing alerts to device- or location-specific teams.
-
Avoid including sensitive information in the body or subject.
-
Keep subject lines concise and descriptive for visibility.
-
For formatting consistency, test email templates with real payloads in a dev environment.
Use Cases
-
Alert operators of safety-critical events in real time.
-
Email daily or weekly reports to management teams.
-
Route fault codes to maintenance teams based on region or device.
-
Send audit logs or summaries to compliance stakeholders.
FAQ
Q: Can I send to multiple recipients?
A: Yes. Use user groups, a comma-separated list in “Send to email”, or a JSON array under a dynamic key.
Q: What if no recipient method is defined?
A: The node will not send any email and will log an error. At least one recipient method is required.
Q: Can I send HTML in the email body?
A: Basic formatting is possible, but rendering may vary. For complex styling, use plaintext summaries or formatted JSON.
Q: Does this node support attachments?
A: Not at this time. For file delivery, consider using the File Output node or export to cloud storage.