How Salesforce Email Alerts Work:

Email alerts are reusable components that combine an email template with recipient specifications. Once created, they can be invoked from multiple automation tools—Flow Builder, Process Builder, Workflow Rules, or Apex code. For a complete walkthrough, see our Salesforce email alert guide.

Components of an Email Alert:

  • Email Template: The message content, including subject line, body text, merge fields for personalization, and formatting
  • Recipients: Who receives the email—record owner, creator, related contacts, specific users, roles, public groups, or additional email addresses
  • From Address: The sender identity (current user, org-wide email address, or default Salesforce address)
  • Object Association: The Salesforce object (Lead, Contact, Opportunity, Case, etc.) that triggers the alert

Creating Email Alerts in Salesforce:

Step 1: Navigate to Setup → Email → Email Alerts → New Email Alert

Step 2: Enter a description and a unique name for the email alert

Step 3: Select the object this alert applies to (Lead, Contact, Opportunity, etc.)

Step 4: Choose an email template—create one first if needed, with appropriate merge fields

Step 5: Configure recipients: select from available recipient types (owner, creator, roles, users) or add specific email addresses

Step 6: Optionally set the From Email Address using an org-wide address for consistent branding

Step 7: Save the email alert—it's now ready to be called from automation

Triggering Email Alerts:

  1. Flow Builder (Recommended):
    Add an Action element in your flow and search for "Email Alert." Select your preconfigured alert and map the record ID. Flow Builder offers the most flexibility for complex email automation scenarios with branching logic and scheduled paths.
  2. Process Builder (Legacy):
    In the Immediate Actions or Scheduled Actions section, select "Email Alerts" and choose your alert. Note: Salesforce is retiring Process Builder—migrate to Flow Builder for new projects.
  3. Workflow Rules (Legacy):
    Add an Immediate or Time-Dependent Workflow Action of type "Email Alert." Classic approach with limited functionality—use Flow Builder for modern implementations.
  4. Apex Code:
    Developers can invoke email alerts programmatically using Messaging.sendEmailMessage() with the email alert ID for custom scenarios requiring code-based logic.

Common Email Alert Use Cases:

Lead Assignment Notifications: Alert sales reps when new leads are assigned to them, including lead details and source information for immediate follow-up.

Case Escalation Alerts: Notify supervisors when cases exceed SLA thresholds, priority increases, or customer sentiment indicates dissatisfaction.

Opportunity Stage Updates: Alert management when deals advance to the negotiation stage or close—keeping leadership informed of pipeline progress.

Approval Request Notifications: Notify approvers when items require their review—discount approvals, contract reviews, or expense authorizations.

Customer Communications: Send automated triggered emails confirming form submissions, acknowledging support requests, or providing order status updates.

Renewal Reminders: Use scheduled emails to alert account managers before contract expiration dates, enabling proactive renewal conversations.

Email Alerts vs Flow Send Email Action:

Use Email Alerts When:

  • You need reusable email actions called from multiple automations
  • Consistent formatting via email templates is required
  • Multiple recipient types need the same message
  • Legacy workflow rules or Process Builder are still in use

Use Flow Send Email Action When:

  • Dynamic recipient selection based on flow logic is needed
  • Custom subject lines or body content vary per scenario
  • No predefined template exists, or one-time emails are required
  • Maximum flexibility for complex scenarios is needed

Email Alert Best Practices:

  • Use Descriptive Names: Name alerts clearly (e.g., "Lead_Assignment_Rep_Notification"), so admins understand their purpose
  • Test Templates Thoroughly: Verify merge fields populate correctly and formatting displays properly across email clients. Use sandbox environments for testing before production deployment
  • Check Opt-Out Fields: For external recipients, ensure your automation checks opt-out status before triggering alerts
  • Use Org-Wide Addresses: Configure a professional From address rather than individual user emails for consistent branding
  • Monitor Delivery: Track email metrics and bounce reports to ensure alerts reach recipients
  • Document Your Alerts: Maintain documentation of all email alerts, their triggers, and business purposes
  • Ensure Compliance: Follow CAN-SPAM and GDPR requirements by including unsubscribe links in external-facing alerts and honoring opt-out preferences

Email Alert Limitations:

Email alerts count toward Salesforce's daily email limit of 5,000 single emails per day. Alerts use basic templates without advanced design capabilities. Tracking is limited compared to dedicated email campaign tools—no open tracking on workflow-triggered alerts by default. For advanced email analytics and higher volumes, consider native AppExchange solutions.

Key Takeaways

  • Email alerts are reusable workflow actions that send templated emails when conditions are met
  • Create alerts in Setup → Email → Email Alerts, then call them from Flow Builder or other automation
  • Use Flow Builder for new implementations—it offers the most flexibility and is Salesforce's recommended approach
  • Email alerts count toward daily limits—consider AppExchange solutions for high-volume needs

Need more powerful email notifications? MassMailer extends Salesforce email alerts with unlimited mass email sending, advanced drip campaigns, real-time tracking, and Flow Builder integration. All 100% native to Salesforce with best-in-class email marketing capabilities.

Start your free trial today →