Skip to content
The main formula of the pack that converts your Coda page or canvas column content into email friendly HTML code.
Share
Explore
Formulas
CreateEmail()
Required inputs
content
The page, canvas, or content used to create the email.
Optional inputs
preText
Pre-header text displays next to the subject line in most inboxes. With HTML emails, there is a lot of code. Some email clients mistake the code for content and display that in the summary. This pre-header text is essentially invisible with a font size of 0, but email clients will see it clearly as content and display it as the inbox preview. Think of it as a secondary subject line or tag line.
highlightColor
Highlight applies a custom color to headers, buttons, and links. You can add a color in either HEX "#ff6b35" or RGB "rgb(255, 107, 53)". The pack is actually very lenient here and does a good job normalizing all colors, so the following ways of adding a color will all work, "#333333", "333333", "#333", "333", "rgb(33, 33, 33)", "33, 33, 33".
style
Style overrides are an easy way to completely change the look and feel of your email. These are pre-programmed and all you have to add is the name of the style for it to work. You can see the available styles and how to use them on the page.
width
The email width in pixels is customizable. Any value between 600 and 900 can be used, with the default being 600. The reason for limiting the range is that it’s easy to run into unintended layout issues depending on things like screen size and email client rendering. The general standard is 600 pixels because it ends up being a good breakpoint for responsive styling for mobile devices.
rowLimit
The maximum number of rows in a table before truncation with the default being 100. It’s easy to end up with thousands of rows in a table, but that many rows would never render in an email. This is a limit added to avoid ever running into that issue. Your table in Coda can display as many rows as you want, but the email will only process up to this limit. Raise this limit with caution and consider adding a link below the table that takes people to the actual table in Coda if you need to show more rows.
proMode
Configuration overrides as JSON for advanced customization. This is a power user feature, but an easy builder is also offered so anyone can take advantage of it. Check out the page for more details. If you want full control over everything from the padding around images to font color, this is where it’s all available to you.
colorMap
Color map overrides as JSON for mapping Coda colors to custom colors. Coda has color options you can choose for various things like text color and table conditional formatting. There is a standard set used for you to click on quickly, but these may not match what you want in your email. The color map parameter allows you to override these colors, so when red is chosen as the text color, you can assign a different shade of red or a completely different color wherever that red is used.
Coda also only exports the light mode colors even if you’re viewing Coda in dark mode. Because dark mode styles are fun and popular, these are mapped as well. If the body background of an email style is sufficiently dark, the dark mode mapped colors will be used.
sendingClient
Some email clients strip various code from HTML before sending it. This parameter allows you to state which client you’re sending from and will include the best coding practices available that will confidently flow through that sender.
An example is Gmail, which strips all MSO conditionals and all mso inline styles before sending. Gmail is the default sendingClient as it’s the most commonly used, but if you’re sending through Outlook, you can use outlook and if you’re sending through an email newsletter service like Mailgun or Sendgrid, you can use service.
The sendingClient parameter wins over a ProMode setting. The reasoning is that ProMode offers strict style control, but what system the email is sent through is a run time decision and the parameter is the easiest and quickest path.
Required inputs
people
People listed as 'Name|PhotoURL' pairs separated by commas. This parameter is called “people” as that’s the most common use case, but any Text|ImageURL pairing will work. Supported image types are PNG, JPG, and JPEG. This is an email client limitation, not a pack limitation.
CreateFacepile(
[List or table column of People Values].ForEach(
Concatenate(
CurrentValue.Name,"|",CurrentValue.Photo.ToText()
)
)
)
Optional inputs
color
Border color for images (HEX '#FFFFFF' or RGB 'rgb(255, 255, 255)').
limit
Maximum number of images to show before displaying moreMessage (default 50).
moreMessage
Custom message when maximum number of faces is exceeded. Use {count} for the number of remaining people. The default is "+{count} more".
size
Size of each profile image in pixels. The default is 36.
sendingClient
Some email clients strip various code from HTML before sending it. This parameter allows you to state which client you’re sending from and will include the best coding practices available that will confidently flow through that sender.
An example is Gmail, which strips all MSO conditionals and all mso inline styles before sending. Gmail is the default sendingClient as it’s the most commonly used, but if you’re sending through Outlook, you can use outlook and if you’re sending through an email newsletter service like Mailgun or Sendgrid, you can use service.
The sendingClient parameter wins over a ProMode setting. The reasoning is that ProMode offers strict style control, but what system the email is sent through is a run time decision and the parameter is the easiest and quickest path.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.