Send Email

Email the rows to people: one message per row, per group, or one for the whole run, with the data attached as CSV or Excel.

Category: Output
Connection: SMTP (Email)
Also known as: burst, distribute, report, send, smtp, mail merge, notify a customer, statement, dunning, invoice, attachment, recipient

What it does

Emails the rows to people. Every other output writes to a system (a file, a database, an API); this one writes to an inbox. Group the rows by a column and each group gets its own message carrying only its own rows, attached as a spreadsheet you did not have to write out first. It is not the same thing as notifications: those tell whoever runs Trinium that a run finished, and carry no data.

Inputs and outputs

Inputs	One.
Outputs	Delivery.

When to use it

Send each regional manager their own workbook, on a schedule, in one run
Email a customer their own statement or overdue-invoice detail
Route rejected rows from Data Validation back to the vendor who has to fix them
Put a Data Compare difference report in front of the team that owns the discrepancy

Examples

One email per region

What makes one email: One email per group · Group by: region

Two regions, two emails. Each one attaches only that region's rows, with no separate write step.

The recipient comes out of the data

To: {{ manager_email }}

Anything in {{ }} is an expression, the same language Filter and Formula use. In group mode it must resolve to the SAME address for every row in a group, or the run is refused before anything is sent.

A subject that says something

Invoice {{ invoice_no }}: {{ days_overdue }} days overdue

Holes are evaluated, not pasted, so {{ round(balance, 2) }} and {{ upper(region) }} work too.

A conditional line in the body

{{ CASE WHEN days_overdue > 60 THEN 'This account is now with collections.' ELSE '' END }}

A hole is a full SQL expression, so a whole sentence can appear or not appear per recipient.

Name the attachment after the group

Attach the rows as: Excel · File name: {{ region }}-statement

Produces North-statement.xlsx and South-statement.xlsx. The extension is added for you.

Tips

A Test run NEVER sends. It renders every message against your real data and lists what it would have sent in the Messages tab (recipients, subjects, attachment names and sizes), so you can check your templates with nothing leaving the building. Use Run when you mean it.
Maximum messages is required, and it is the point: state how many emails this node may send in one run. If a run would exceed it, nothing is sent at all rather than the first N.
Everything is checked before the first message goes out: every address, every template, every group. A configuration mistake sends zero emails. What is NOT pre-checked is the network: if the relay starts refusing halfway through, the ones before it have already gone.
Separate several addresses with a SEMICOLON, not a comma: a comma is legal inside a display name like "Smith, John" <j@acme.com>.
The Delivery output carries one row per attempted message: recipient, subject, status, error, rows covered and attachment size. Wire it to a table and you have a send log; leave it unwired and a Test run still shows it in the Data tab.
A row whose recipient renders empty is skipped and counted, not treated as an error: a missing address is a fact about the data.
The relay is a connection, separate from the alert relay in Settings, so business mail can go out on its own server and its own From address. Its Test button signs in for real and sends nothing.
Whoever manages the connection can fill in Allowed recipient domains (acme.com, partner.com). Every To, Cc and Bcc address is then checked before anything goes out, and one address outside the list refuses the whole run, so nobody receives anything until the data or the list is fixed. The match is exact: acme.com does not include eu.acme.com. Blank means any recipient.
Office 365 starts refusing above about 30 messages a minute. Set Messages per minute if you are sending a lot.