Send Richer Email with the ‘Send Better Email’ Flow Action

Send Better Email is the latest and best email action for Flow, replacing previous versions of Send Rich Email and Send HTML Email.

It provides easy access to Salesforce’s single and mass email services, taking the place of Flow’s built-in Send Email action, which is currently something of an underachiever.


This flow action supports:

  • Rich HTML email bodies that can use all of the capabilities of Flow’s Text Templates, including Bold, Italics, Underline, Bullets and Numbers, Left/Center/Right justification, URLs, images, fonts, and text size
  • Email Templates (both Classic and Lightning) with field merge and letterheads
  • Any combination of the following input sources, for To, CC, and BCC
    • A single email address
    • A string collection of email addresses
    • A collection of Contacts
    • A collection of Users
    • A collection of Leads
  • Organization-Wide Email Addresses
  • Attachments
  • Ability to toggle on/off the use of the Salesforce per-user email signature
  • Ability to provide a plain text body, an html body, or both
  • Ability to set the ReplyTo email address and the Sender Display Name
  • Multi-Language Support for Lightning Email Templates

In addition, this action provides access to Salesforce’s Mass Email services. These don’t provide as much configurability but allow for greater manageability and throughput.

Currently unsupported features include:

  • Character Set setting

If you’re interested in extending this class, please do so!

Usage Notes

This Action greatly expands the range of what you can do with Flow and email, but keep in mind that Flow is not optimized to serve as a mass email marketing solution. Despite the range of options provided here, you may hit system limits. Consider Marketing Cloud for large volumes and specialized needs.

NOTE: Scratch/Sandbox/Development orgs have very limited volume and recipient restrictions (example, scratch orgs have strict cutoff after sending just 50 email messages) and may allow as few as 10 external email addresses per day. Your production org will vary significantly, and issues related to limits in development do not necessarily correlate with production environments.


Salesforce provides two kinds of email service, referred to here as Single Message and Mass Message modes.

Choose Standard or Mass Email for Action

In a nutshell:

  1. Standard Email – The preferred choice. When in doubt, select this option. It provides far more powerful customization options for recipient selection (including the use of standalone text email addresses), message formatting, and more. However, this mode limits the number of recipients (150) per message and the number of different messages per invocation (10) you can use.
  2. Mass Email – If you’re sending the same message to many recipients of the same object type (e.g., contacts, leads, or users), and you’re comfortable being required to use an email template, this mode provides you with greater throughput.

You can change between the two, but the parameters are very different, so changing the mode is almost a complete “configuration from scratch” process.

Sender Settings

These parameters are related to the sender of the message.

Set Sender Settings

You can either 1) use an OrganizationWideEmailAddress or 2) specify your own Reply-To Email Address and Sender Display Name. If you provide an OrganizationWideEmailAddress, that will take precedence and any Reply-To Email Address and/or Sender Display Name you’ve also provided will be ignored.

Sender Display Name

Optional. The name that appears on the From line of the email. Don’t attempt to set this if you’re also using an Organization-Wide Email Address with a defined DisplayName field.

NOTE: By default, the message will usually appear to be coming from (Example):; on behalf of; Do Not Reply <> . Changing this involves your email domain settings, outside of Salesforce.

Organization Wide Email Address

Optional. The ID of the organization-wide email address associated with the outgoing email.

  • Note: The object’s DisplayName field cannot be set if the Sender Display Name field is already set.
  • Note: you cannot use Organization-Wide Email Address together with Reply Email Address.

To use an Organization-Wide Email Address , pass the Id of one that you have defined into the action via the “Use This Organization-Wide Email Address Id”. (If you want to get the benefit of Verified sending, you can’t just paste the email address into the Reply-To Email Address field. You have to use the Use This Organization-Wide Email Address Id field.). You can locate the ID in the URL of an Organization-Wide Email Address (it starts with ‘0D2’):

Sender receives BCC of first email sent?

If selected, the user running the Flow receives a copy of each email that is sent.

Reply Email Address

Optional. The email address that receives the message when a recipient replies. Can not be used at the same time as an Organization-Wide Email Address.

Use Salesforce Signature if executing user has one?

Each Salesforce user can set up their own signature in their personal settings:

If this checkbox is set, the user’s signature will be appended to the bottom of the email. The default is true.

Set Addressees

You can use the following data sources:

  • A single text email address
  • A string collection of email addresses
  • A collection of Contacts
  • A collection of Users
  • A collection of Leads

To simply type in a text value, select “String Variables (or type an address)” in the Search existing Flow resources, type the value you want to use, and click Search

Add a new address as a string

Subject and Body

You can directly configure the subject and body or alternatively use a Lightning or Classic Email Template.


NOTE: If you manually specify a Subject and select Use Email Template, your specified subject value will override the Template’s specified Subject. Emails without a subject (either specified or part of the template) will not be sent/delivered.

Specifying the Email Body

You can create static or custom bodies, and can use plain text and/or rich, HTML text. You can type the text directly into the HTML Body and Plain Text body fields, but it’s generally better to create Text Template flow resources and craft your body there, and then select the Text Template from the HTML Body and Plain Text combo boxes.

Rich Text HTML email bodies can use all of the capabilities of Flow’s Text Templates, including Bold, Italics, Underline, Bullets and Numbers, Left/Center/Right justification, URLs, images, fonts, and text size.


Text Template Resource named “HTMLTextTemplate”
HTMLbody Parameter in sendBetterEmail Action

Plain Text (Body)

Not everyone has HTML email access, so even when you’re sending out an HTML email, it’s wise to also specify a plain text version. You cannot use plainTextBody and a template.

Previous versions of SalesForce allowed for templates which automatically attached text-only versions in the event a recipient did not desire and/or have the capability to use HTML-based email. As of this writing, it appears the Lightning Email always sends the HTMLBody, but does not attach the plainTextBody.

Using an Email Template

Email templates with merge fields let you quickly send emails that include field data from Salesforce records like contacts, leads, or opportunities and simplify the design and approval process for professional communication in appearance and content. You can use email templates when emailing groups of people— mass email—or just one person.

For details about using Email Templates, see the section – Using Email Templates.

If you choose to use an Email Template, you can specify it by either its Id or Name, but you cannot provide both:

This actions has advanced capabilities to support multi-lingual templates. If you’re using this, you must use Template Name with the Template Language. For further details see section – Using Email Templates. Lightning Email templates (accessed by Apps–>Email Templates) are recommended for this language feature.

  • Email Template Id – You can get the Template Id from the Email Template URL. The Id would be ’00X2F000001RDHPUA4′ in the below example.
Finding Email Attribute for Parameters
  • Template Name – The name of the Template (In the above example, ‘sendHTMTest’). If you have multiple Templates with the same name, the Action will select the first one.
  • Template Language – To use this field, add the phrase ‘Language =”[language name]”‘ to the Description field of your email templates. If you specify a Language in tht eTemplate Language field, it will , it will look for the first Template with a matching “Language” tag in the Email Description field.

Recipients & Recipient-Related Records

This section only appears when you’re using a template.

Recipient Record Id (also for template merge fields and recording related Email as an activity)

Required if using a template. The ID of the contact, lead, or user to which the email will be sent.

Related Record Id (for template merge fields and/or recording Email as a task)

The ID of a record associated with the recipient.

This value must be the record ID of one of the following object types:

  • Account
  • Asset
  • Campaign
  • Case
  • Contract
  • Opportunity
  • Order
  • Product
  • Solution
  • Custom

This field essentially allows the template to draw merged values from two records: that of the recipient and that of a separate record.


You can attach files to your emails using a collection of ContentDocumentLink records. To learn how to attach documents using Content Document Links, see this.

Record as Activity and/or Task

Note: Using this feature does require a record access/query which will be counted for limits).

Save Email as Activity on Recipient Record(s)?

If you used a collection of records (or a single Recipient record Id) as the addressee(s), this will cause the email send to be recorded as an Activity on that recipient record.

Save Email as Task on recipient related record(s)?

If selected, a Task will be created on the Related Record (not on the Recipient Record).

Mass Email Configuration

When you set the Email Type to ‘Mass Email’, you get to configure fewer things but you get some monitoring capabilities including the ability cancel sends and get notified when sending is complete. To begin with, you must use an Email template to specify your email content.

Specifying Recipients

Set Sender Settings

With the following exceptions, these values behave the same as in the Single Email example above.

Description (sent in internal email with status after action completes)

When you use Mass Email, a summary report gets sent to the running User upon completion of the sending. The body of this message will include the value specified in the Description input. It is used so the receiver (usually an admin) can distinguish which Action this came from. It should not be confused with the Email Template Description.

Email Template

This section behaves the same as in the Single Email case, described above.

Specifying Recipients

Recipient Record Id Collection – To specify recipients, pass a collection of Contacts, Leads, or Users to the “Recipient Record Id Collection” input.

Related Record Id Collection – Use this only if you are providing a collection of Contacts for Recipient Record Id Collection. If you use it, it must: 1) match the number of Contacts in umber and 2) be from one of the following: Contract, Case, Opportunity, Product. Essentially, this surfaces additional merge field options in the Template.

Record as Activity and/or Task

When sending a communication, you may wish to keep a record that a communication has been sent. To do so, you can use one or both of the following. Note: Using this feature does require a record access/query which will be counted for limits).

Save Email as Activity on Recipient Record(s)?

If selected, the sent email will be recorded as an Activity on the corresponding Recipient Record (not on the Related Record).

Save Email as Task on recipient related record(s)?

If selected, a Task will be created on the Related Record (not on the Recipient Record).

Output Values

Both Single and Mass Email return values that can be used later in the flow.


A string which reports back the last error encountered in executing the action. In the event a successful send occurs, errors on subsequent events (such as adding a task or email activity) may be reported here, but isSuccess would still return true.


A boolean that indicates the success or failure of this Action in executing the send email. In the event a successful send occurred, errors on subsequent events (such as adding a task or email activity may be reported in the errors), but isSuccess would still be true.


If “Save Email as Task on recipient related record(s)?” has been selected, this is a returned list of TaskIds that were successfully created. If an error occurred for the individual task, instead of an ID, it will return a string starting with “ERROR: ” followed by the error message.


In the case where a Template name was used instead of a specific id, this parameter returns the Id of the template actually used. This is useful if the process maintainer wishes to know which language template was used (in the case of language localization) or which template was selected if the org has multiple templates of the same name


Using Email Templates

This action supports Email Templates . For a nice introduction on how to use email templates, letterheads and even graphics, you may wish to start with the Trailhead: Configure an Email Letterhead and Template.

Use Email Templates to save time and standardize email sent by you or others in your organization. Use merge fields or enhanced letterhead to customize the content and/or appearance of the communication. Details on how to use EmailTemplates in multilingual environments can be found here.

There are 3 core components of an email template:

  1. The Template. The template contains the format of the email (including Letterhead) and syntax for merging fields into that communication. A merge field is a placeholder in an email template or letterhead. When you send the email, the placeholder is replaced with the Salesforce data from the record or records of the people you are emailing. Fields that can be merged include those from the TargetObject, another sObject record, and global variables. NOTE: the merging done by the template system is different from the merging done by Flow, and there is currently limited ability to pass dynamic values from Flow into the template system. HOWEVER, see this post for an easy technique that will allow you to get full rich dynamic merging.
  2. The Target Object Record. This is who the email is being sent to, usually a Contact, User, Lead or Group. Depending on the type of template you are using, other fields from this Target Object can also be merged into the template as part of the send email (e.g., Dear Dear {{{Recipient.Name}}}). In email templates, the merge fields for “recipient” come from the specified object Id.
  3. The Related Record (for Contacts only). If you specify a Contact for the Target Object  field, you can specify an optional Related Record  to merge fields in the template from that record. For the most predictable results, Use the Handlebars Merge Language in Lightning Email Templates and Enhanced Letterhead which merges fields from the record into the email using the format {{{[Related Record Type].[Field]}}} (e.g.,  {{{Case.CaseNumber}}}), and convert your Classic Templates to LightningEmailTemplates with Enhanced Letterhead.
Classic Template

Lightning Email Template

Adding Multilingual Email Template Support

SendBetterEmail provides multi-lingual support within the same flow by allowing a set of related email templates to be created in different languages. In the flow, specify the desired language. To make this work, the names of the email templates must follow some rules:

  • Each language localization has its own template with all localizations sharing a common EmailTemplate.Name.
  • To differentiate the localizations, add the following text to the EmailTemplate’s Description fieldt: ‘Language=”en_US”‘ (or whatever corresponding to your organization localizations).

For more on how to add localization to an email template set, please refer to Send Better Email with Multi-Language Support for Lightning Email Templates.

Operational Considerations

This action makes use of the standard Salesforce email infrastructure, the same service that you use when you send a single email directly from a lightning experience page or a classic case feed. As such, any emails you send will be included in your usage, so be aware of the limits and guidelines. (Developer note: this action makes use of the Apex Messaging service API’s.)

This action does not use or involve Email Alerts, which are used in Workflow Rules and exist in Flow as separate actions you can drag into your flow. Be mindful of this so you don’t accidentally confuse the Email Alerts, the Email Templates, and the Flow Text Templates.



MVP Jeremiah Dohn pioneered this space several years back with his well received HTML Email Flow action. The version here is similar and adds a several of additional capabilities.

Jack Pond is the primary maintainer of this action.

Related Actions

Get Group Info: User Emails and More



Before installing this component you need to have on your org the Flow Base Components support package.

Install that here.

2.0.1 Unlocked sendBetterEmail The first full Custom Property Editor version that supports both singleEmail and massEmail and has several fixes.

If you are having trouble updating/upgrading the component, you may want to look at: Tips & Tricks – Update/Upgrade an Unmanaged Package

Old versions

Note: Versions prior to v1.33.2 use this documentation.

  • 1.33.2 Unmanaged sendHTMLEmail (with Flow Examples/Tests) – Major upgrade that includes several enhancements and bug fixes. Parameters are now selected using a Custom Property Editor. Additionally, mass email messaging has been included.
  • 1.33.1 Unmanaged sendHTMLEmail (with Flow Examples/Tests) – Minor update Addresses issues  #308 and #316 to fill in Task Comments and Recipients and improved documentation.
  • 1.33.1 Unmanaged sendHTMLEmail(Without Examples) – Core Component without Examples/Flow Testing (Added documentation, validations)

Source Code

Source code

Notify of
Inline Feedbacks
View all comments
Josh Dayment

Jack this looks amazing but it looks like the install link is pointing me to version 1.33.1


Should the FlowComponents and sendHTMLEmail package be installed as ‘all users’ or admin’s only? Unclear what limiting this type of package would mean to real life use. If I as an admin build a flow using the SendHTMLEmail, but didn’t install it for all users, will my end users not be able to kick off a flow that uses an action from the package?


It looks like package version 1.33.2 is incorrectly linking to version 1.33.1. Please make 1.33.2 available.

[…] Pond has added major improvements to email sending via Flow with Send Better Email – Flow Action. This action replaces all previous rich/html Flow actions. Most notably, the new action features a […]

[…] This action has been updated. See the new version here. […]

[…] The latest version of this is available here. […]


I’m having an issue with v2.0.1 and sending to one email address.

I’ve configured the component like this:
comment image
comment image
comment image
This prevents activation with the following error:

These issues prevent activation.

  • Email_Error_Better (Action) – The type for the input parameter “SendTOthisOneEmailAddress” doesn’t match the type for the assigned value.

Am I doing something wrong?

Last edited 1 month ago by Gary

Jack, I tried setting a string variable as the TO address, however after creating the variable with a default value, then selecting it in the flow component, as soon as I selected the variable to use, I saw this error message:
comment image

I closed the error and unselected the variable in the component, saved and refreshed the browser tab. After this, I was able to select the string variable in the component without error. Saving and testing worked fine, and I’m now using this workaround.
Thanks for the quick feedback.


Thank you so much, Jack (and pioneer, Jeremiah Dohn) ! Is this the ‘equivalent’ of 1.33.2 or is this a new thing? If you can remove your bias, is it best for those who have used 1.33.x to use 1.33.2 OR is 2.x stable enough to make the switch? Would love some expert advise.

Filip Tuma

Hi Jack,

thanks a lot for this great tool! This widens the scope of what I can achieve on the platform significantly 🙂
I just ran into a minor bug concerning the appended signature: there was no way to send without signature, because while the box isn’t checked it still defaults to true. Just changing the code in line 56 from true to false did th trick for me:
 Boolean useSalesforceSignature = curRequest.useSalesforceSignature == null?false:curRequest.useSalesforceSignature;
Now I can actually send without signature.
I hope this may help!

Kind regards,


Thanks Filip,
I hadn’t realised that the emails were including signatures. I’ve also applied the change you mention to resolve this in our org.


I tried to deploy this change to the SendBetterEmail apex class using change sets, but I run into this error during deployment validation:

Cannot add component of type:ApexClass named:SendBetterEmail subjectId:01p3j0000062cF3 to another package because it is an installed component.

I have the package installed in production already, and cannot edit the apex class directly in production.

Any tips on how to deploy this ‘fix’?


Thanks Jack,
I’m hesitant to migrate all my flows away from sendHTMEmail just yet due to the couple of issues that have been discovered in sendBetterEmail.

Is it likely that an update for sendBetterEmail will be published soon to resolve these issues, particularly the signature inclusion issue? That way I can simply update sendBetterEmail for now and continue evaluating it, while maintaining my flows that use sendHTMEmail.

Filip Tuma

Not sure if this is still relevant, but I made the fix in a sandbox and could validate and deploy without any further changes, except for the value in line 56. I used and it took all of 5 minutes to get it to work.

Josh Dayment

When trying to add an attachment I get this I have a record collection of Content Document Links in the flow I tried typing out the variable and that does not work either.

Last edited 1 month ago by Josh Dayment
Josh Dayment

Sorry here is the photo


I have the same issue.

adan levy

Hi Jack! Thank you for this update.
I’m migrating from sendHTMLemail, but what I found is that all messages sent via Send Better Email are clipped by gmail (in spite of being very short emails as shown in the attached image).
Same email sent by sendHTMLemail arrives to gmail complete without the “clipped” message. When clicking on “view entire message” nothing new or hidden appears
ideas about this?


Are Classic email templates compatible with the newest version? I installed and have been testing in my sandbox, everything works (even getting the ContentDocuments as attachments) except for the email is blank, and the template isn’t used. Even though the debug logs show it as a success. Maybe I need to use Lightning Email template instead?

Camille Eusebio

I’ve been experiencing this as well. Would love to use email templates instead of hard coding the email body within the flow


There appears to be bug in the ‘Attachments’ element. The picker (drop-down) only shows non-collection record variables. When setting a contentDocumentLink variable activation fails with “The input parameter “contentDocumentAttachments” can accept multiple values, so the assigned value must be a flow variable with the isCollection property set to true.” Setting value to a CDL collection variable without picker (drop-down) fails, reverts to previous value.


Jack Pond, I don’t understand, check what? I currently have no way around the the failure and cannot activate the flow because of it. I cannot set a CDL Record collection variable for this field.


Oddly enough after rebuilding the CDL Get Records element toggling from ‘all records’ to ‘first record’, saving then toggling back to ‘all records’ (collection) appears to have resolved the issue. FYI: I had updated from 1.33 to 2.0.1 and replaced the Action node in an existing Flow in sandbox.


So this is definitely a bug but I found the work-around. Build your flow as desired. Once you are ready to set the ContentDocumentsAttachments collection variable in the SendBetterEmail Action element first switch your Get Records element to “Only the first” (non-collection) so it appears in the SendBetterEmail picklist, select and close, switch Get Records element back to a collection (all records), save flow. If you have to filter the Get Records collection(list) of records you have to build a temporary filtered list then assign this back to the Get Records variable. Entering a collection variable without using what the… Read more »


This is also affecting me, and I cannot change from the old Send HTML action over to this one.

ChristianS work around also doesn’t work for me as I’m assigning content documents to a collection variable, rather than a get records element.

Megan Moody

I am using this action to allow external users to select which document(s) they would like to be emailed to them. It works great with one exception: if a new version is uploaded for the file, it sends BOTH version 1 and version 2 of the document. Is there any way to just send the most recent version? It seems that both versions share the same ContentDocumentLink.Id. I’m hoping I’m missing something really obvious. Thanks in advance!

Megan Moody

I’m not sure how I would do that. When a new version is uploaded, both versions are associated with the same CDL. If you mean that I should upload it as a new file, that works, but now it’s another file on that account and we don’t want people to not know which is the correct version to use.


When using a typed BCC email address the following error is thrown when saving the flow, preventing activation:

“The type for the input parameter “SendBCCthisOneEmailAddress” doesn’t match the type for the assigned value.”


This is a known issue, and is being addressed. Use a variable reference instead of a typed string.

Tara Cobb

It’s not allowing me to use a typed string or select a variable in the TO: address. The search does not return any variables.

Screen Shot 2020-09-03 at 8.42.46 AM.png

Wonderful. Thank you for addressing this for the next person. I have since implemented a simple variable with a default value.

In general I want to congratulate all involved on this wonderful effort put forth on this project. Without this I’d been spending a lot more time building these components myself or just retaining an Apex class for this part. You make flow much more usable. Thank you.

kc fellger

Hi Jack – we’re really liking what this can almost do in our NPSP instance. Our use case is to allow account managers to decide which email address on a contact that they want to send to (such as Work Email). I’ve built a working choice set (thanks to Quick Choice FSC) and can insert the selected / desired address in the TO: resource via string variable – however, the component is also forcing the ‘Email’ address field as a secondary recipient. We don’t abide by the Preferred Email field updates so at times the Email field is blank –… Read more »

kc fellger

Hi Jack – yes, I’m using Lightning Email Templates. Initially I tried one with the Related Entity as Contact – then I tried Account, and then no Related Entity. In all 3 scenarios the generic Email address is included as a secondary recipient even if I specify Work Email as the recipient.


First things first: a HUGE thanks for this action, Jack, which is hugely needed by who? Every-effing-one on Salesforce? I wanted to report few improvements/bugs: if the Lightning Email Template has no Description, the line 535 of SendBetterEmail if (thisTemplate.Description.Contains('Language="')){ quite logically crashes. Maybe a good use for the new “?.” operator in Apex? filling in the subject line in the Flow action prevents the usage of the defined template (love being able to reference by name, btw!): maybe a small explanation in the form would help? I had few issues with defining the To: selecting my single record variable… Read more »


Using Classic Email Templates injects extra line breaks in the rendered/sent email. Is this a known issue? Does a work-around exist for this problem?


What’s the best practice when sending to a record collection set of contacts, and using a template? How do I provide recipient context for the template using the Recipient Record ID field?


Hi Jack,
Thanks for the advice, however I should clarify my question. I was actually asking how to configure this action in the scenario where the ‘To’ field has been set to a record collection set, containing multiple recipient contacts. How do I reference one single contact ID in the ‘Recipient Record ID’ field, so that I can utilise sending using lightning templates? I can’t think of a way to pick out the ID of the contact the action is currently processing.


It’s not currently possible to send to a contact record variable. When I select the record variable as the To value, I get the following error upon save: These issues prevent activation.Warning: Send_Email_Better (Action) – The input parameter “SendTOtheEmailAddressesFromThisCollectionOfContacts” can accept multiple values, so the assigned value must be a flow variable with the isCollection property set to true. As per the docs, I see this isn’t currently supported, however I would expect that I could still use the email field value from this record variable to define the To value. However I am unable to enter a reference to… Read more »


In the Recipient Record Id field, I’m unable to reference values from loops.
comment image
The same reference is valid within assignment elements. Would be nice if this action supported these loop references so that I didn’t have to use an assignment element to convert the value to a reference that is supported.

[…] example, having dependent inputs is awesome. If one value is X, show input Y. Applying this to the Unofficial Send Richer Email Action is a perfect […]


I would really like to use this action to send lightning email templates that use lead object records as the related record.

Currently, if I set the ‘Related Record Id’ field to that of a lead record, the following error occurs:

INVALID_ID_FIELD – Invalid entity type for whatId.

Please can support for the lead object type be added?

Stuart Burke

Jack, I am hitting an issue when trying to assign a string collection to the BCC address

Uncaught Error: property name is not defined
throws at

Seems to be working for the TO and CC fields. Full disclosure am working in a trailhead playground for POC reasons. Attempted the same set up in the sample flow, changing the curContacts collection to the stringCollectionEmaiAddressesl collection and hit the same issue.

Any thoughts?

Andrew Porter

Love this component and will needed for Flows. Though I am having an issue. I want to use a Lightning Email Template, and providing in config, but the sent email is blank. Looked at the debug logs and it seems to me that the email is fired successfully, plus, it gives the template which is used.

Any ideas on why, or how I could get to the root cause

17:30:39.515 (608456634)|VARIABLE_SCOPE_BEGIN|[343]|thisResponse|SendBetterEmail.Response|true|false
17:30:39.515 (608509199)|VARIABLE_ASSIGNMENT|[343]|thisResponse|{"isSuccess":true,"templateUsed":"00X3H000000MGPMUA4"}|0x3ae8485c

Many thanks


How do I get the string variables dropdown in the “TO”, “CC” and “BCC” fields to show up?

Ideally I would have liked to be able to search for a variable like the sendHTMLemail allwoed in the “SendTOthisOneEmailAddress” field