A Send Email node sends one email for each incoming item, with a subject, body, and attachments built from that item. Use it to notify a team when a partner's file has been processed, to deliver a converted report to the people who read it, or to alert on the Error path when a file could not be processed.

Send Email accepts file items or data items. It sends through your Custom SMTP server, so the messages come from your own address and mail service. A site without Custom SMTP cannot save an Automation that contains a Send Email node.

Settings

To Addresses takes one or more recipients, and every field on the node accepts a TransformScript template, so a recipient can come from the data item, as in {{ payload.recipient }}, and a subject can name the file, as in Processed {{ attributes.name }}. Subject and Message Body are optional. From Address, CC, and BCC are under Advanced Settings.

Attachments takes the paths of files on your site to attach, and the paths are templates too, so {{ attributes.path }} attaches the incoming file itself. Attachments totaling more than 25 MB fail the item with the error processing-failure/attachment-too-large before the message is sent.

What the Next Node Receives

Send Email passes its items on unchanged, with the outcome recorded on each item.

Errors

A message the mail server did not accept fails that item. Error Handling rules on the node determine what happens to a failed item.

Send Email vs. Email Notifications

Email Notifications tell Users or Groups on your site about file activity in a folder, in batches as often as every 5 minutes. Use a notification when people need to know that files changed in a folder. Use a Send Email node when the message is built from the item, with a subject that names the file or a body built from values in the data, when one message is sent per item as it is processed, or when the recipient is an address outside your site's users.