Email

Audience: Business Users, Low-code Engineers

Skill Prerequisites: HTML, Tokens

The Email actions send email from your application, such as notifications, confirmations and documents, with tokens to personalize each email.

Choosing an action

Action	What it does	Use it to
Send Email	Sends an email, with optional attachments, through the site's SMTP settings or an SMTP connector.	Send a confirmation to a user, or notify an administrator when a form is submitted.

More email actions in add-ons

Add-on	What it adds	Use it to
Email OAuth	Send Email (OAuth Compatible), which sends through the site's DNN mail provider instead of an SMTP server.	Send email on a site whose mail server requires OAuth sign-in, such as Microsoft 365 or Google Workspace.
Mailchimp	Actions that add people to a Mailchimp audience and record their marketing permissions.	Add newsletter sign-ups from a form to Mailchimp.
Email Sync	IMAP and POP3 triggers for Automation jobs.	Process incoming email.

Send Email connects to an SMTP server: the portal's or host's SMTP settings, or the server in the SMTP connector you pick. It supports custom headers and display names such as Support <support@mydomain.com>, and adds a plain-text version to HTML emails. Send Email (OAuth Compatible) doesn't support these. See Email OAuth for the differences.

Sending to many people

• Send mail to all users sends a separate email to each user loaded in the context, for example by Load Users from SQL. [User:...] tokens refer to each recipient. CC and BCC get one copy per user.
• For recipients that aren't users, load them into a list and send inside Execute Actions for each List Entry.
• Recipient fields support tokens. If their values come from a form, a user can add other addresses. Use [User:Email] or fixed addresses when you can.

For text messages, see Twilio and Clickatell. For team notifications, see Slack.

Revised 10/02/2026