When Salesforce Flow is used to trigger email alerts using the Email Alert action, the sent email is not automatically logged as an activity on the record's Activity Timeline. This means there is no automatic record in the Activity Related List showing that the email was sent via Flow automation. This article describes two approaches to track emails sent through Salesforce Flow: (1) adding a Create Task action to the Flow to manually log the activity, and (2) using the Send Email action in Flow, which supports automatic activity logging to records including leads, contacts, accounts, and opportunities.
To log a task activity when a Flow sends an email alert, add a Create Records element to your Flow that creates a Task record simultaneously with the email alert. Configure the Task as follows:
Once the Flow is triggered, the email alert is sent and a completed Task activity is logged on the record at the same time.
As of a recent Salesforce release, the Send Email action within Flow supports automatic email logging to a record's Activity Timeline. Unlike the Email Alert action, the Send Email action can log the email directly to a recipient record (leads, contacts, or personal accounts) or to a non-recipient record (such as an Account or Opportunity), or both.
Note: This automatic logging feature is only available when using the Send Email action in Flow (not the Email Alert action), and must be configured individually for each Send Email action element in the Flow.
Email alerts generated by automation systems such as Process Builder or Workflow Rules do not automatically get stored in Salesforce's Activity Timeline. Using the Send Email action in Flow is the recommended approach for email communications that require activity tracking.
Flow Element: Send Email
000385146

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.