This action sends an email to one or multiple recipients. It also supports sending attachments along with the body of the email. The content of the email can be configured for each recipient when sending to multiple addresses.
Typical Use Cases
Send email notifications
Send confirmation emails
Email Campaigns with the help of our BeeFree integration
Don't use it to
- Debug - Use Log Error or Log Debug Message
|Load Users from SQL||Load multiple users so you can send emails to all of them at once|
|Load Entities (CSV File)||Load emails and other data from a CSV file to compose complex emails|
|Load Entities (CSV)||Load emails and other data from a CSV formatted text to compose complex emails|
|Load Entities (Excel File) XSLX||Load emails and other data from an Excel file to compose complex emails|
|Load Entities (JSON)||Load emails and other data from a JSON formatted text to compose complex emails|
|Load Entities (SQL)||Load emails and other data from the database to compose complex emails|
|Load User||Load an user so you can obtain recipient information via tokens|
|Execute actions on entity list||Execute a set of actions for each entity, that can help you to compose complex emails|
Input Parameter Reference
|From||The email address from which the email(s) will be sent||Yes||No|
|To||Recipient(s) to send the email to. Multiple Recipients can be separated by semicolon (;)||Yes||Yes|
|Send email to all users||Sends emails to all users in the context loaded by Load Users from SQL||No||No||No|
|Reply To||Email address that the reply message is sent back to instead of the ||Yes||No|
|CC||Carbon Copy. Multiple Recipients can be separated by a semicolon (;) or a comma(,)||Yes||No|
|BCC||Blind Carbon Copy. Multiple Recipients can be separated by a semicolon (;) or a comma(,)||Yes||No|
|Format||The format of the email. Check below for more details||No||No|
|DNN email template to use.||Choose from a predefined email from the system||No||Unset||No|
|Subject||The subject of the Email||Yes||Yes|
|Body||The email content to send||Yes||No|
|Headers||Appends custom headers to the email.||Yes||Unset||No|
|Attach Portal Files||Picks existing files from the system to send as attachments.||No||Unset||No|
|Attach Field #||Form only parameter. It provides the ability to add up to 5 Single File Uploads fields to be sent as attachments.||No||Unset||No|
|Attach from Token||Computes file path from token. It must be relative to the portal home folder. Multiple items must be separated by semicolons or commas.||Yes||No|
|Ignore Errors||If errors are ignored, the submission of the form continues even when there is an error sending the email. Otherwise, an error message will be displayed to the user. Note that if the email is being sent async or is placed in a pickup folder, errors won't be caught.||No||No||No|
|HTML (And replace newline with ||To simplify the input of the email we are replacing the newlines in the |
|Text||Regular text, with no formatting options such as bold, italics, underlines, or special layout. Can include URLs, such as http:// and ftp:// options.|
|HTML(Recommended)||It’s the way web pages and email templates are coded so that text is formatted and images are added. What it is displayed in the HTML editor of |
Note that this presents a security risk when the
Reply To parameter have tokens from untrusted sources.
The above-mentioned parameters support tokens so if the values are not coming from a trusted source they may be altered and email recipients can be modified.
For example, if you let the user input the email address manually from a Form, it may present a security risk. The expectation is to input only one email address but the end-user may input:
firstname.lastname@example.org;email@example.com. Doing this he may send the emails that are meant only for him to other people or organizations. To avoid similar situations we strongly recommend using Tokens like
[User:Email] or hardcoded email addresses when setting recipients parameters.
The FROM parameter needs to be in concordance with the application SMTP settings. (eg:
For Plant An App cloud-hosted application, the
From address can be
firstname.lastname@example.org or an address from a custom domain, if configured.
1. Simple Email
Send a simple email
2. Simple Email with Tokens
In this simple example, we use tokens to send the email from the current user to itself. This is done using the
[User:Email] token. We also use the
[User:FirstName] and the
[User:LastName] tokens to create a dynamic email body.
3. A more complex setup for sending an email
In this example, we demonstrate how to use a mix of text and tokens to set parameters.
Note how the
From parameter can be configured to also have a display name, such as
The Sender of the Email<email@example.com>. Same applies to any email field.
In addition, we set up a token for the logo so we can send it with the email as an attachment.
4. Send an email to a list of recipients retrieved from the database
In this example, we will load all the existing users directly from the database and send them an email. Note that we are using the
Send mail to all users parameter instead of setting the