---
schema_version: "1"
id: 7eb944137f2a445c04132c23d6348990abd885a20570f66f941e9408bcf816c8
title: Send an Email from a Flow Using an Existing Email Alert
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_flow_build_send_email_email_alert.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_flow_build_send_email_email_alert.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d3d1511db1c38abe1d619c62549dd964e83d3f030e1650172b36177bcc6c6be9
description: If you're using an email alert in a Workflow Process or Process Builder process, you can use the existing email alert in a flow. The email alert works the same whether it's triggered by a flow, a Workflow Rule, or a Process Builder process.
products:
- Flow Builder
- Salesforce Platform
release: "264"
---
# Send an Email from a Flow Using an Existing Email Alert
If you're using an email alert in a Workflow Process or Process Builder process, you can use the existing email alert in a flow. The email alert works the same whether it's triggered by a flow, a Workflow Rule, or a Process Builder process.
### Required Editions
To open, edit, create, activate or
deactivate a flow using all flow types, elements, and features available in Flow
Builder, including Einstein and Agentforce for Flow:
Manage Flow
Note You don't need to be an admin to have the Manage Flow permission. Ask your admin to add it to your profile or permission set.
Note If you want to send an email using the email body in the Send Email action, see [Send an Email from a Flow](https://help.salesforce.com/s/articleView?id=platform.automate_flow_build_send_email_from_a_flow.htm&release=264.0.0&type=5 "Compose your email's subject and body directly in the Send Email action element, without an email template. You can send to any email address and use merge fields from any object in your org.").
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).
1. Open the Flows list view.
- From the Automation app, select the **Flows** tab.
- From the **Flows** tab in any Lightning app, click the actions menu and select **Open Flow**.
- From Setup, in the Quick Find box, enter Flows, and then select **Flows**.
Note that the Automation app and Flows tab options don't require Setup access.
2. Create the type of flow that you want to use.
- From the Automation app, click **New**, then click the category, and then the flow type. For example, to create a record-triggered flow, click **Triggered** | **Record-Triggered Flow**.
- From Setup, click **New Flow**, then click the category, and then the flow type. For example, to create a screen flow, click **Screens** | **Screen Flow**..
3. Configure the Start element if needed for the flow type.
4. Add and configure an Email Alert action element.
1. Click , and then search for and click the name of your email alert. For example, click **Hot Account Alert Owner**.
2. For Label, enter a name for your email alert element. For example, Email Account Owner. Let the API name autofill.
3. For Record ID, search for and click the resource that holds the ID of the record associated with the email alert. For example, if your email alert's Object is set to Account, select a resource that holds an account record ID.
5. Save and name the flow.
6. To make sure that the flow works as expected, debug and test it by using different scenarios.
7. To start sending emails, activate the flow.
Important After migrating flows, always review and reconfigure the Send Email action to reference the new record IDs in the target Salesforce org. This step prevents broken references and makes sure that email delivery functions correctly after migration.