- Body. Create a Text Template variable to store the email body in rich text as it supports formatting text and adding merged fields
- Subject. Create a Text Template variable if you want to use merged fields in the subject line. Otherwise, a regular text variable or even a constant will suffice.
- Recipient Email Addresses (collection or comma-separated). You can include one of the two. In the screenshot above, the email is only going to one user and the body contains a greeting with the recipients name but you can opt to use a comma-separated variable if your message is the same for every recipient. However, if the message is the exact same for every recipient, use a collection rather than a comma-separated variable.
- Rich-Text-Formatted Body. True if you want a rich text body and False if you want to send the email in plain text.
- Sender Email Address. This is optional. You only include a value when you want to use a OrgWideEmailAddress.
- Sender Type. This is optional. If you don’t include it, the email is sent from email address of the current user running the Flow. There are two possible options for this field at the time of this writing.
- DefaultWorkflowUser. The email is sent from the email address of the default workflow user email address.
- OrgWideEmailAddress—The organization-wide email address that you specified in the Sender Email Address field.
eduardo ⦿ pro 