Email Content Builder Recipe(s)

[jkranz-rk]

Summary

I'd like to see an implementation of LWCs intended for use in the Lightning Email Template Content Builder.

The LightningStatic__Email target has been available to create custom components for this builder for some time, but only available for Pardot customers. In Spring 22, this target became available more generally.

As such, we are interested in leveraging this capability. Based on the LWC Developer Guide documentation, it seems there are a variety of special considerations and limits on what you can do with custom components in this target, and it isn't super clear how to really leverage it for real world applications.

Suggested Solution

I'd be interested in seeing something that demonstrates:

• Leveraging Apex during merge (is that possible?). For example, a custom component that displays a table/list of records related to the primary record getting merged into the template.
• Examples of the markup available to the configuration xml file that appears to be special for this target

Alternative Solutions

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Welcome! 👋

Thank you for posting this issue. 🙇🏼‍♂️ We will come back to you latest within the next 48h (working days). Stay tuned!

[satyasekharcvb]

Thank you, @jkranz-rk! we will review and implement the recipe.

[KarlLivesey]

any update on this.

[mitchspano]

There are a lot of open questions that we have regarding LightningStatic_Email target for LWCs.

When playing with these components, it feels like almost anything you do can break the email template:

• Try to use a getter to define a variable? breaks
• Try to import an Apex method? breaks
• Try to use @wire notation? breaks (at least this one is documented)

The community would benefit from some examples of how LightningStatic_Email target should be used and what is possible when this is the target. Right now, this seems to provide little benefit over the out of the box HTML component, but perhaps that is a consequence of my lack of understanding of what is possible.