Email

Sends emails through a configured email connection.

Purpose

Creates emails from table data or one summary email for the entire dataset. Supports recipients, CC, BCC, formatted text, the input table and attachments.

Inputs and outputs

A target with in and optional success/failure outputs. Sending takes place while writing the active target.

Parameters

Parameter	Settings and values	Options and limits
`role`	Block role: a source reads data; a target writes the result.	Default: `target`
`connection_id`	The saved connection through which the block accesses the system.	Default: `empty` Up to 64 characters
`to`	Main recipient addresses or a template using a row field.	Default: `empty` Up to 4000 characters
`cc`	CC addresses.	Default: `empty` Up to 4000 characters
`bcc`	BCC addresses.	Default: `empty` Up to 4000 characters
`to_people`	UBC Data Bridge users and roles for main recipients.
`cc_people`	Users and roles for CC.
`bcc_people`	Users and roles for BCC.
`subject`	A single-line email subject; supports tags.	Default: `empty` Up to 998 characters
`body`	The email body, including formatting and table substitution.	Default: `empty` Up to 100000 characters
`format`	text or html; a new editor block uses formatted text.	Options: `text`, `html` Default: `text`
`attachments`	Attachments from File Manager, a folder or the run parameters’ “Attached file” field.	Count: 0–20
`time_zone`	The time zone for system date and time substitutions.	Default: `Europe/Kyiv` Up to 64 characters

Templates and message count

The substitution {{Назва поля}} uses the current row’s value. System tags: {{$date}}, {{$time}}, {{$datetime}}, {{$flow}}, {{$rows}}, {{$row}}, {{$table}}.

If any recipient, subject or body template contains a row field or {{$row}}, a separate message is created for every row. Otherwise, one message is created for the entire input.
{{$table}} is available only in the message body. It includes up to 1000 rows and an indication of the remainder.
All fields used in tags must exist in the input; TEMPLATE_FIELD_MISSING is detected during preparation.
Dates and times use the specified time_zone. Data values are escaped for formatted messages.

Step-by-step configuration

Create and test an SMTP connection. Add a block using it.
Set recipients using addresses, a field tag, or users/roles.
Write the subject and body; insert tags from the available-field list.
Check the hint showing whether there will be one email for the dataset or one per row.
Add attachments and the time zone. Check preparation in a simulation before sending.

Rules and diagnostics

Addresses of users and role members are read from their current profiles during the run.
The subject cannot contain line breaks; tag names are validated.
Up to 20 attachment sources; the same source cannot be added twice. An attachment from a parameter field is absent if the user did not add a file.
A File Manager folder adds the files it contains at run time.
External delivery can have a partial or uncertain result. Before rerunning after an error, check the log to avoid duplicate emails.
An empty active input does not create a message: EMPTY_STAGE. Up to 10000 messages are allowed per block per run; for more, filter or split the dataset.
Losing the response during external sending is treated as an uncertain result: the system does not automatically resend that message.
Separate addresses with commas, semicolons or line breaks. At least one recipient and a non-empty subject are required; up to 500 recipients per email in total. Duplicates across “To”, “CC” and “BCC” are removed.
A folder attachment adds up to 100 files. The total email size, including attachments, is limited by the SMTP connection setting.

Configuration example

For a CustomerEmail, CustomerName, Amount table, set to={{CustomerEmail}}, subject=Your report, body=Hello, {{CustomerName}}. Amount: {{Amount}}. This creates an email for every row. For one summary, use a fixed address and “Processed {{$rows}} rows. {{$table}}” as the body.