This article explains how to create an email alert for "Person Accounts" using a Record-Triggered Flow. This process replaces the retired Workflow Rules functionality.
While direct email alerts on Person Accounts aren't a standard feature, you can create a simple Flow to automate this. This method works for both newly created and edited records.
1. Create a New Flow
Navigate to Setup, type "Flow" in the Quick Find box, and select Flows.
Click New Flow.
Select Record-Triggered Flow and click Create.
2. Configure the Flow's Start Element
Object: Select Account.
Trigger the Flow When: Select A record is created or updated.
Set Entry Conditions:
Condition Requirements: All Conditions Are Met (AND).
Field: IsPersonAccount
Operator: Equals
Value: {!$GlobalConstant.True}
Optimize the Flow for: Select Actions and Related Records.
3. Add the Send Email Action
On the Flow canvas, click the + icon on the path after the Start element.
Select Action.
In the Action search bar, select the Send Email action.
4. Configure the Email Action
Label: Give your action a descriptive name, like "Send Alert to Person Account".
Body: Enter the text for your email. You can use a New Resource and select Text Template to create a rich email body with merged fields.
Subject: Enter the email subject line.
Recipient Email Addresses (comma-separated): This is the key step. Enter {!$Record.PersonEmail}. This tells the Flow to send the email to the email address on the Person Account record that triggered the Flow.
Click Done.
5. Save and Activate the Flow
Click Save in the top right corner.
Give your Flow a Flow Label (e.g., "Email Alert for Person Accounts") and an API Name.
Click Save, and then click Activate.
To trigger this Flow on records that existed before activation, you'll need to perform a mass update on those records.
000386755

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.