---
schema_version: "1"
id: fc5f6ef555523ad44c19c4dfa51ba9acce7e3fccc4e09d1b325ec91868e1521c
title: Email Alert Element
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_ref_elements_emailalert.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_emailalert.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ff6e5a6b890422a8481404648f4bb60467520a14acd5bd73827e3f6a46d47845
description: Send an email using an Email Alert action where you specify an email template and a static list of recipients. You add an Action element to your flow and search for the name of your already configured Email Alert action.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Email Alert Element

Send an email using an Email Alert action where you specify an email template and a static list of recipients. You add an Action element to your flow and search for the name of your already configured Email Alert action.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.flow_ref_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions and user interfaces that support Flow Builder. Some Flow Builder features integrate with other Salesforce products that require additional licenses.">View supported editions.</a></td></tr></tbody></table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png)

Note If you're using Marketing Cloud Growth, use the Send Email Message action instead of the Email Alert action. Email Alert actions don't work with segments.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important To send email from Salesforce, the Send Email action in Salesforce Flow requires domain-level and user-level email verification. Email delivery fails if either the user's email address or the email-sending domain is unverified. See [Requirements to Send Email from Salesforce](https://help.salesforce.com/s/articleView?id=xcloud.security_email_verification_requirements.htm&language=en_US&type=5).

Before you begin:

- Create a [Lightning email template](https://help.salesforce.com/s/articleView?id=sales.email_templates_lightning_parent.htm&language=en_US) or [Classic email template](https://help.salesforce.com/s/articleView?id=sales.admin_emailtemplates.htm&language=en_US). Specify the recipient record in any merge fields you use. For example, you could use the contact record or the lead record. When you build the email Alert, you match the object to the referenced record in the flow. For example, if the email alert references the Lead object, use a lead record ID when configuring the element in the flow.
- In Setup, search for Email Alerts and configure your [email alert](https://help.salesforce.com/s/articleView?id=platform.customize_wfalerts.htm&release=264.0.0&type=5 "An email alert is an email generated by an automated process and sent to the designated recipients. The action consists of the standard text and the list of recipients. You can use an email alert in an automation, such as a flow, approval process, or entitlement process. Legacy workflow rules and processes built in Process Builder or through the Invocable Actions REST API endpoint also use email alerts."). See [Email Alert Actions](https://developer.salesforce.com/docs/atlas.en-us.api_action.meta/api_action/actions_obj_email_alert.htm) in the Actions Developer Guide.
- Understand the [daily limits](https://help.salesforce.com/s/articleView?id=platform.workflow_limits_email.htm&release=264.0.0&type=5 "The daily allocation for emails sent through email alerts is 1,000 per standard user license per org—except for free Developer Edition and trial orgs, where the daily workflow email allocation is 15. The overall org allocation is 2,000,000. This allocation applies to emails sent through email alerts in workflow rules, approval processes, flows, processes, or REST API. Single emails sent to external email addresses are also limited, and how those limits are enforced depends on when your org was created.") for emails sent from email alerts.
- Determine which record you want to reference in the email and use that record's ID in the element. For example, if you’re sending the email to the contact that triggered the flow, use the ID of the triggering contact. Or, if you’re using a Get Records element to get the record that receives the email, use the ID of the record found in the Get Records element. If the email alert has merge fields, the referenced record is the starting point for those fields.

Add an Action element to your flow. Search for your email alert using the name of the email alert and select the email alert to configure. To filter the list of email alerts by a specific object, enter the API name of the object. The unique name for each email alert is prefixed with its object. For example, email alert emailAlert-Account.Owner\_Changed is associated with the Account object.

## Set Input Values

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:17.825311942959%">
          <col style="width:82.174688057041%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d299159e123">Field</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d299159e126">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d299159e123 ">
              <strong class="uicontrol">Record ID</strong>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d299159e126 ">
              <p>Select a resource that contains the ID for the record that you want the email
                to reference. If the email alert uses merge fields, this record is the starting
                point for those merge fields.</p>
              <p style="margin-bottom:0;">This field accepts single-value resources of any
                type. The value is treated as text. The object of the referenced record must match
                the object of the email alert. </p>
            </td>

          </tr>
        </tbody>
      </table>

## Usage

At run time, the email isn’t sent until the interview’s transaction is completed. Transactions are complete when the interview either finishes or runs a Screen, Local Action, or Wait element.

Flow Builder displays email alerts from managed packages only if the email alert isn’t protected.

#### See Also

- [Sending Emails from a Flow](https://help.salesforce.com/s/articleView?id=platform.flow_build_actions_email.htm&release=264.0.0&type=5 "Send emails to your customers, partners, and employees automatically in a flow. There are several different ways to send an email from a flow depending on who you want to send your email to and how you want your email content to look. Determine the best way to send your email based on the functionality that you need.")
- [Customize What Happens When a Flow Fails](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault.htm&release=264.0.0&type=5 "Learn how fault paths customize what happens when a flow fails. Choose how to notify admins, guide users, and take a follow-up action.")
- [Move and Connect Elements to Change a Flow Route](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_route_add.htm&release=264.0.0&type=5 "Identify which elements the flow runs and in what order by connecting the elements on your canvas together. To change the run order, move elements and add or remove connectors.")
- [Daily Allocations for Email Alerts](https://help.salesforce.com/s/articleView?id=platform.workflow_limits_email.htm&release=264.0.0&type=5 "The daily allocation for emails sent through email alerts is 1,000 per standard user license per org—except for free Developer Edition and trial orgs, where the daily workflow email allocation is 15. The overall org allocation is 2,000,000. This allocation applies to emails sent through email alerts in workflow rules, approval processes, flows, processes, or REST API. Single emails sent to external email addresses are also limited, and how those limits are enforced depends on when your org was created.")