You are here:
Send Email Action
Send and optionally log an email to records by defining the email content and recipients in a flow.
Required Editions
| View supported editions. |
In Flow Builder, search for Send Email in the element menu, and select Send Email.
Set Input Values
To set the inputs for the email, use values from earlier in the flow. Specify at least one recipient email address in the Recipient Addresses, CC Addresses, BCC Addresses, or Recipient ID fields. For more information about setting up a Send Email action, see Sending Emails from a Flow.
Configure Recipient Details
To configure a recipient in your email flow, use these input parameters.
| Input Parameter | Description |
|---|---|
| Recipient Addresses | Optional. A comma-delimited list or a collection of the recipients' email addresses. This parameter accepts single-value resources and collection variables of type string, and treats the value as a list of text values. If Log Email on Send is True, the flow logs the email to the ID that you specify for Recipient ID, not to the records associated with the email addresses in Recipient Address List. The maximum size for this field is 4,000 bytes. For flows that use Send Email Action version 1.0.1 and earlier, separate input fields for the address list and address collection are available. You can enter values for BCC Addresses, CC Addresses, Recipient ID, and Recipient Addresses as long as the combined number of recipients is 150 or fewer. |
| CC Addresses | Optional. A comma-delimited list or a collection of recipient email addresses to send a copy of the email to. CC recipients are visible to all recipients. This parameter accepts single-value resources and collection variables of type string, and treats the value as a list of text values. The maximum size for this field is 4,000 bytes. For flows that use Send Email Action version 1.0.1 and earlier, separate input fields for the address list and address collection are available. You can enter values for BCC Addresses, CC Addresses, Recipient ID, and Recipient Addresses as long as the combined number of recipients is 150 or fewer. |
| BCC Addresses | Optional. A comma-delimited list or collection of recipient email addresses to send a copy of the email to. Other recipients can't see BCC recipients. This parameter accepts single-value resources and collection variables of type string, and treats the value as a list of text values. The maximum size for this field is 4,000 bytes. For flows that use Send Email Action version 1.0.1 and earlier, separate input fields for the address list and address collection are available. You can enter values for BCC Addresses, CC Addresses, Recipient ID, and Recipient Addresses as long as the combined number of recipients is 150 or fewer. |
Configure Sender Details
To configure a sender in your email flow, use these input parameters.
| Input Parameter | Description |
|---|---|
| Sender Type | Optional. The type of sender that sends the email. Valid values are:
|
| Sender Email Address | Optional. The organization-wide email address that’s used to send the email.
Use this parameter only when you set the Required when:
This parameter accepts a single-value resource of any type, and treats the value as text. |
Configure Email Content
To configure the email content in your email flow, use these input parameters.
To create your email content, use the Compose Email Content option under Configure Email Content.
To use an existing email template, use the Use Email Template option under Configure Email Content.
| Input Parameter | Description |
|---|---|
| Subject | The subject of the email. Required for flows that use Send Email Action version 1.0.1 and Compose Email Content option. Hidden for flows that use Send Email Action version 1.0.1 and Use Email Template selected. For flows that use Send Email Action version 1.0.0, this field is optional if you use an email template. The email template overrides the entry in this field. And, required if you don’t use an email template. Enter text or select a single-value resource of any type that contains your content, for example, a Text Template resource. The flow treats the value as plain text. |
| Body | The body of the email. Required for flows that use Send Email Action version 1.0.1 and Compose Email Content option. Hidden for flows that use Send Email Action version 1.0.1 and Use Email Template selected. For flows that use Send Email Action version 1.0.0, this field is optional if you use an email template. The email template overrides the entry in this field. And, required if you don’t use an email template. Enter text or select a single-value resource of any type that contains your content, for example, a Text Template resource. If you
don’t use an email template, the flow treats the value as plain text or rich text,
depending on your selection in Rich-Text-Formatted Body. If
you select True for |
| Rich-Text-Formatted Body | Optional. Indicates whether you want the resource specified for the Body parameter to use rich text. Valid values are:
Hidden for flows that use Send Email Action version 1.0.1 and Use Email Template selected. |
| Use Line Breaks | Optional. Indicates whether to render the line breaks in the
rich-text-formatted body text template. Valid values are Hidden for flows that use Send Email Action version 1.0.1 and Use Email Template selected. |
| Email Template ID | The ID of the Classic or Lightning email template to use for the email subject and body. Required for flows that use Send Email Action version 1.0.1 and Use Email Template option. Optional for flows that use Send Email Action version 1.0.0. Hidden for flows that use Send Email Action version 1.0.1 and Compose Email Content selected. If the email template has merge fields from an object other than the one associated with Recipient ID, specify the record used to supply those merge fields in Related Record ID. To use this parameter, specify the Recipient ID. You can use this parameter with Log Email on Send. Using email templates in the Send Email action changes the API called by the action, which changes the daily email send limit to the General Email Limit instead of the Daily Workflow Email Limit. |
| Email Template Name | Optional. The name of the Classic or Lightning email template to use for the email subject and body. Available for flows that use Send Email Action Version 3.0.1 and later when you select Use Email Template. When deploying flows between environments, use Email Template Name instead of Email Template ID to preserve the reference to the selected email template and eliminate manual record updates. Including an Email Template Name requires the Recipient ID. If the email template has merge fields from an object other than the one associated with Recipient ID, specify the record used to supply those merge fields in Related Record ID. Using email templates in the Send Email action changes the API called by the action, which changes the daily email send limit to the General Email Limit instead of the Daily Workflow Email Limit. |
| Attachment ID | Optional. A comma-delimited list of attachment IDs in the email. Enter a value or select a single-value resource of string type that contains the list of attachments. This parameter accepts single-value resources of any type and treats the value as text. The attachment ID can be the ID of a Document, Content Version, or Attachment items. Adding attachments with the Send Email action changes the API called by the action, which changes the daily email send limit to the General Email Limit instead of the Daily Workflow Email Limit. |
| Attachment ID Collection | Optional. A collection of attachment IDs. Select a collection resource variable of text type that has a list of attachment IDs. The attachment ID can be the ID of a document, content version, or attachment item. Adding attachments with the Send Email action changes the API called by the action, which changes the daily email send limit to the General Email Limit instead of the Daily Workflow Email Limit. |
| Recipient ID | The ID of a lead or a contact record. Required if you specify Email Template ID. If you include Log Email on Send, this parameter is the ID of the person to send and log the email to. If you include Email Template ID, this parameter is the ID of the person to send an email to and populate recipient merge fields with. If you specify Recipient ID, then you must also specify Email Template ID, Log Email On Send, or Attachments. If the ID entered in this parameter is a lead record, you can’t use Related Record ID. The maximum size for this field is 4,000 bytes. You can enter values for BCC Addresses, CC Addresses, Recipient ID, and Recipient Addresses as long as the combined number of recipients is 150 or fewer. |
| Related Record ID | Optional. The ID of a non-recipient record. For example, it can be the ID of a case record. If you include Log Email on Send, this parameter is the ID of a secondary record to log the email to. If you include Email Template ID, this parameter is the ID of the non-recipient record used to populate email template merge fields. If you enter a lead record ID for the Recipient ID, then you can’t use this parameter. |
| Log Email on Send | Optional. Indicates whether to log the email on the specified records’ activity timelines and activity history. Valid values are:
Hidden until you provide a value in Recipient ID or Related Record ID. To log an email, specify a value for Recipient ID, Related Record ID, or both. You can use this parameter with Email Template ID. Logging emails with the Send Email action changes the API called by the action, which changes the daily email send limit to the General Email Limit instead of the Daily Workflow Email Limit. To prevent recursive loops in flows triggered on the EmailMessage object, disable Log Email on Send in asynchronous flow paths. Enabling this option creates a new email message record, which triggers the flow again. |
| Add Threading Token to Body | Optional. Indicates whether to create a unique token for the related record and add it to the email body. Hidden until you provide a value in Related Record ID. When the related record is a case record, Email-to-Case uses the token to link future email responses to that case. To link future email responses
to other records, create an Apex Email Service and use the
If you define a Template ID, the flow doesn’t insert any token into the email body. Instead, use merge fields with your template to populate data. |
| Add Threading Token to Subject | Optional. Indicates whether to create a unique token for the related record and add it to the email subject. Hidden until you provide a value in Related Record ID. When the related record is a case record, Email-to-Case uses the token to link future email responses to that case. To link future email responses
to other records, create an Apex Email Service and use the
If you define a Template ID, the flow doesn’t insert any token into the email subject. Instead, use merge fields with your template to populate data. |
Using a Send Email Action
To use a Send Email action in a flow, see Sending Emails from a Flow.
Transaction and Email Deliverability Information
At run time, the flow doesn’t send the email until the interview’s transaction completes. Transactions are complete when the interview either finishes or executes a Screen, Local Action, or Wait element. Before activating your flow, confirm that your org can send email in Setup | Deliverability | Access to Send Email (All Email Services) | All email.
- If you set Email Deliverability to No Access and you don't set Email Template ID or Log Email on Send fields, the flow runs but doesn't send the email.
- If you set Email Deliverability to No Access and you set Email Template ID or Log Email on Send fields, the flow returns an error when it sends the email.
Considerations
- Emails sent by using the Send Email action don't include email signatures from My Email Settings. To include a signature, add one to the email template, flow text template, or other resource used in the Send Email action.
- If the Related Record ID is set as a Case ID by the flow,
Customer Community users can't create an
EmailMessagerecord. For details, see Experience Cloud User Licenses. - The Send Email action doesn't send emails when you debug the flow in Rollback mode.
- The flow creates emails up to 35 MB, including attachments. If the size exceeds 35 MB, the flow fails at run time.
- To export a flow using API version 64.0 and earlier, change the Send Email action version to 1.0.1. To fix version change errors for recipient address fields, delete the warnings and repopulate the parameter. To export a flow using Send Email action version 2.0.1 and later, specify API version 65.0 or later in the sourceApiVersion field in the sfdx-project.json file.
- If a recipient email address field contains a variable that’s empty at run time or the recipient email address belongs to an inactive user, the flow returns a "Probably Limit Exceeded or 0 recipients" error. For resolution details, see Knowledge Article: Error 'Probably Limit Exceeded or 0 recipients' in a Flow with a Send Email or Email Alert Action.
Setup Configurations for Scheduled Flows
If you use the Send Email action element in a Scheduled-Triggered flow, configure the organization-wide email address in Setup.
- Set the organization-wide email address in Setup | Email | Organization-Wide Email Addresses.
- Add the organization-wide email address in Setup | Process Automation Settings | Automated Process User Email Address.
Email Sending Limits
- If you use Log Email on Send or Email Template ID, the daily email send limit is based on the single email limit. See General Email Limits.
- If you don’t use Log Email on Send or Email Template ID, the daily email send limit is based on the daily workflow email limit. See Proactive Alert Monitoring: Daily Workflow Email Limit.
- Each licensed org can send single emails to a maximum of 5,000 external email addresses, or recipients, per day. A day is based on Greenwich Mean Time (GMT).
- Sending emails to internal email recipients doesn't count toward the org daily limit.
Handling IDs During Flow Migration
When you configure a Send Email action in a flow, you reference records such as email templates and attachments by using their unique record IDs. These IDs are specific to the Salesforce org where they're created.
When you migrate flows from one org to another, such as from a sandbox to production or between different environments, the record IDs of these assets change. As a result, any references to the original template or attachment record IDs in the Send Email action become invalid.
After migration, you must manually update the flow to reference the newly created template or attachment IDs in the target org.
