Best way to create and maintain html for email activity?

asked on April 20, 2022

Hello Everyone,

I have been playing with creating better-looking emails that come from the Workflow email activity. I have seen many posts about how the email activity acts with normally formatted HTML syntax. I myself have found the only way to get the HTML to look the way I want is to have all "code" smashed up in 1 long line. This is no fun when working with the Assign Token activity that I'm using to create the body of the email. One idea I came up with that I think is a little better is to have a text file in my repo that Workflow can retrieve text on and use that token in the body of my email. But after testing, I get the same limitation that I can't have that text file formatted normally and I need to remove all spaces and newlines. The end result is a long string in my text file but it's still better editing than making edits in the token box.

Has anyone come up with a better way to maintain an HTML file to use in an email activity? Is there a way I can keep the formatting and use some technique to prep the HTML for the email activity? Thanks for the help everyone.

0 0

replied on April 20, 2022

Update Word Document. The activity has an option to give you the document contents as HTML to be used in email messages. If you check "emit email token" in its advanced properties, it will give you an "email" token you can use to populate the email body.

Note that the whole email body has to be only this token.

Bonus though, you don't have to mess with HTML, you can just use Word formatting and when you want to make changes, you only need to upload the updated Word doc to the server.

3 0

replied on February 21, 2023

A simpler approach is to insert the following (for example) at the start of the email:

and adjust the format tags you want to use for the entire email.

Then follow the email text with:

</div>

0 0

Question

Question

Best way to create and maintain html for email activity?

Replies

Sign in to reply to this post.