Email Alert
An Email Alert is a Salesforce automation component that sends a pre-configured email when triggered by a Workflow Rule, Process Builder, Flow, or Approval Process.
Definition
An Email Alert is a Salesforce automation component that sends a pre-configured email when triggered by a Workflow Rule, Process Builder, Flow, or Approval Process. Each Email Alert pairs an Email Template with a list of recipients and the underlying object that triggers the message. When the rule, process, or flow fires the alert, Salesforce merges the template with data from the triggering record and sends the email to the configured recipients. Email Alerts are how Salesforce automation produces customer-facing communication without writing Apex.
The configuration lives in Setup, then Email Alerts: pick the object (Case, Lead, Opportunity), pick the email template (Classic Email Template, Lightning Email Template, or Visualforce Email Template), and define the recipients (Roles, Users, Groups, Email Field on the record, Email Address). The alert is then available to Workflow Rules, Process Builder actions, Flow Send Email elements, and Approval Process actions. A single Email Alert can serve multiple automations, so well-named alerts become reusable building blocks.
How Email Alerts work in Salesforce automation
The components of an Email Alert
Each Email Alert has three core configurations. First, the object: the alert can only be used on automation tied to that object. Second, the Email Template: a Classic or Lightning template that defines the email''s subject, body, and merge fields. Third, the recipient list: a combination of Roles, Public Groups, individual Users, the record Owner, email fields on the record, or hardcoded email addresses (up to a configurable limit per alert).
Email Templates and merge fields
Email Templates define the message content. Lightning Email Templates (added in 2018-plus) support rich formatting and embedded merge fields. Classic Email Templates are older but still widely used. Visualforce Email Templates are the most flexible, supporting Apex variables and dynamic content. Each template type works with Email Alerts; pick based on the complexity of the message and your org''s existing template inventory.
Recipient configuration patterns
Common patterns: Send to Record Owner (the User who owns the triggering record), Send to Case Contact (the email field on the Contact related to the Case), Send to Public Group (a group of internal users like Sales Managers), Send to Hardcoded Address (for system alerts). A single Email Alert can combine these: send to the Owner, plus the Account''s Primary Contact, plus a designated Public Group.
Email Alerts in Workflow Rules
Workflow Rules (deprecated) historically used Email Alerts as the primary email-sending mechanism. A Workflow Rule on Case fires when a status changes, with an Email Alert as one of its actions. The Workflow Rule provides the trigger and condition; the Email Alert provides the content and recipients. This pattern persists in many legacy orgs.
Email Alerts in Process Builder and Flow
Process Builder (deprecated) and Flow (current) both consume Email Alerts as actions. In Flow, the Send Email element can use either an Email Alert or its own template configuration. Using Email Alerts is the more reusable pattern: define the alert once, use it across multiple Flows. Building the email in the Flow itself is faster for one-off cases but creates duplication if the same email is needed elsewhere.
Email Alerts in Approval Processes
Each step of an Approval Process can fire Email Alerts: when a request is submitted, when it is approved, when it is rejected, when it is recalled. The Email Alert is configured once and referenced from each step. This is how approval-driven notifications get sent to the relevant parties (the requester, the approver, the next-step approver, the legal team).
Daily send limits and the platform constraint
Salesforce caps Email Alert volume: 1,000 external emails per day per org for most editions, 5,000 for Performance and Unlimited. Internal emails (to Salesforce users) do not count. Hitting the limit silently drops new emails. For high-volume notifications, use Marketing Cloud or a dedicated SMTP integration instead of relying on Email Alerts.
How to create and use an Email Alert in Salesforce automation
Creating an Email Alert is a 5-minute task: pick an object, pick a template, pick recipients. Wiring it into a Workflow Rule, Process Builder, or Flow takes another few minutes. The total time to send a triggered email is under 15 minutes for most use cases.
- Create or verify an Email Template
Setup, then Email Templates, then New. Build a Lightning Email Template with subject, body, and any merge fields. Save and activate the template. If you have an existing template that fits, skip this step.
- Create the Email Alert
Setup, then Email Alerts, then New Email Alert. Provide a clear description (Case_Owner_New_Comment_Notification). Pick the object the alert applies to. Pick the Email Template. Save.
- Configure recipients
On the Email Alert detail page, set the recipients. Pick from Public Groups, Roles, Users, Owner, related records'' email fields, or hardcoded addresses. Add as many as needed; the system enforces per-alert limits.
- Reference the alert from an automation
In a Workflow Rule, Process Builder, or Flow, add a Send Email action and pick your Email Alert from the list. The automation now triggers the email when its conditions are met.
- Test the alert
Trigger the underlying record change in a sandbox: change a Case status, update a Lead Owner, submit an Approval Request. Confirm the email arrives, the merge fields are populated, and the recipients are correct.
- Monitor and audit
Build a report on EmailMessage records to track delivery, or use the Email Logs in Setup to confirm individual alerts fired. Watch for daily-limit warnings if your org sends high volume.
Clear name for the alert. Appears in pick-lists across automation tools.
The Salesforce object that the alert applies to. Cannot be changed after creation.
The content of the email. Picks from Classic, Lightning, or Visualforce templates.
At least one recipient (Owner, Group, User, hardcoded address, or related-record email field).
- Daily limit is 1,000 external emails per day (5,000 for Performance and Unlimited). Hitting the cap silently drops new emails. Monitor send volume in production.
- Email Alerts use the From address configured on the alert, not the running user. Customers see the configured address; pick one that maps to a real inbox if they reply.
- Activating an Email Alert does not retroactively send for past records. The alert only fires when the triggering automation fires after creation.
- Email Alert names must be unique per object. Use clear naming conventions to prevent collisions: ObjectName_Trigger_Notification_Audience.
Trust & references
Straight from the source - Salesforce's reference material on Email Alert.
- Create Email AlertsSalesforce Help
- Lightning Email TemplatesSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is an Email Alert?
Q2. What can trigger an Email Alert?
Q3. Where should you configure Email Alerts in modern Salesforce?
Discussion
Loading discussion…