Send Email
Sends mail. The plainest notification path, and the one that reaches everybody.
Type: notify-email · Category: Notification · Ports: one input · one output
When to use it
- Alarm notification and escalation
- A scheduled report or a nightly summary
- Telling someone a pipeline found something they need to act on
Settings
| Setting | Key | Purpose |
|---|---|---|
| Connection | connectionId | Which SMTP connection. |
| Recipients | recipients | Addresses, or bound from the message. |
| Subject | subject | Templated from the message. |
| Body | body | Templated from the message. |
Example — a critical alarm by email
Alarm (raised, critical) → Send Email
Recipients: {{payload.recipients}}
Subject: [{{payload.priority}}] {{payload.name}} on {{payload.tagPath}}
Body: {{payload.name}} raised at {{payload.raisedAt}}.
Tag: {{payload.tagPath}}
Value: {{payload.value}} (limit {{payload.limit}})
Acknowledge in QUBIQ to stop reminders.
A path that does not exist becomes empty
{{payload.data}} against a message with no data field renders as nothing at all — you get
Value: rather than Value: {{payload.data}}. A raw token arriving in somebody's inbox looks
like data the author meant to send, so a blank is the safer failure.
The practical consequence is that a mistyped path is invisible: the message still sends, just missing a piece. Send one to yourself, or watch a Debug node, before wiring it to an escalation.
The database nodes do the opposite with the same syntax — there an unresolved token is left as literal text.
Gotchas
- Put a filter in front of it. An alarm that flaps every few seconds sends every one of those emails, and the first thing an operator does with a mailbox full of them is write a rule that hides all of them — including the one that mattered.
- Bind recipients rather than typing them — see On-Call Roster, so a shift change is not a pipeline edit.