# Sending emails via workflow with variable Text

**URL:** <https://community.hubspot.com/t/sending-emails-via-workflow-with-variable-text/1322>\
**Category:** Lists, Lead Scoring & Workflows\
**Tags:** email, workflows\
**Created:** [March 20, 2017, 1:30pm UTC](https://community.hubspot.com/t/sending-emails-via-workflow-with-variable-text/1322 "2017-03-20T13:30:05Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![QA1234](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/qa1234/32/38459_2.png) [@QA1234](https://community.hubspot.com/u/QA1234)\
**Post date:** [March 20, 2017, 1:30pm UTC](https://community.hubspot.com/t/sending-emails-via-workflow-with-variable-text/1322/1 "2017-03-20T13:30:05Z")

</div>

Is it possible to incorporate line breaks inside a hubspot email with variable text? Current a list is generated with several bullet points stung together in a sentance. I want to make it a list instead by passing line breaks Char(10) / Char(13) inside the variable text field.

current the text looks like 1. Green Apple 2. Red Apple

I’m wanting the email to be shown as:

1. Green Apple

2. Red Apple

Is this possible?

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [May 25, 2017, 12:48pm UTC](https://community.hubspot.com/t/sending-emails-via-workflow-with-variable-text/1322/2 "2017-05-25T12:48:39Z")

</div>

@QA1234,

What do you mean by line breaks between variable text? Are you using peresonalization tokens within an email in a workflow?

If you share screenshots of what you are trying to do, I can take a look.

Thanks!

---

<div class="post-metadata">

**Author:** ![QA1234](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/qa1234/32/38459_2.png) [@QA1234](https://community.hubspot.com/u/QA1234)\
**Post date:** [May 25, 2017, 1:08pm UTC](https://community.hubspot.com/t/sending-emails-via-workflow-with-variable-text/1322/3 "2017-05-25T13:08:17Z")

</div>

![Untitled.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/f/f/ff975a316bb06f0dbf1c7a54ade2d3c2c3ae2fb7.png)

The CONTACT.ALERT\_VARIABLE2 would be replaced with the contact info changed. Currently it’s passed as [email:me@me.com](mailto:email:me@me.com) Address: 123 Main St Phone: 555-555-5555

What I want the email to do is allow a line break whether I pass a variable to be converted upon render or otherwise.

So can hubspot read [email:me@me.com](mailto:email:me@me.com) ~ Address: 123 Main St ~ Phone: 555-555-5555

and replace the “~” with an HTML line break.

The end result wanted without creating 3 different variables:

email: [me@me.com](mailto:me@me.com)

Address: 123 Main St

Phone: 555-555-5555

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [May 25, 2017, 7:53pm UTC](https://community.hubspot.com/t/sending-emails-via-workflow-with-variable-text/1322/4 "2017-05-25T19:53:00Z")

</div>

@QA1234

If this is information that is being fed into the email through personalization tokens, I would recommend breaking the information into three separate tokens so that you can format it in three separate lines. Otherwise, I believe it will pull in as one continuous line if it is assoicated with one contact token.

---

<div class="post-metadata">

**Author:** ![QA1234](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/qa1234/32/38459_2.png) [@QA1234](https://community.hubspot.com/u/QA1234)\
**Post date:** [May 25, 2017, 8:03pm UTC](https://community.hubspot.com/t/sending-emails-via-workflow-with-variable-text/1322/5 "2017-05-25T20:03:33Z")

</div>

That’s the direction we are going, I was just trying to see if anyone had figured out a way to force hubspot to recognize line breaks inside a single user token. To simiplfy the programming needed to populate this data into an email.

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [May 25, 2017, 8:45pm UTC](https://community.hubspot.com/t/sending-emails-via-workflow-with-variable-text/1322/6 "2017-05-25T20:45:32Z")

</div>

@QA1234,

Not sure there is a way to break it up, as it is pulled in through one token so if you were trying to force a line break there’s no garantee it would populate correctly depending on the formatting of where the token was being used.

If you were curious about the coding behind line breaks (and whether or not it is feasible), I would recommend posting in the design room, as they may have more insight over there for how to format the text.

---

<div class="post-metadata">

**Author:** ![jwiedenheft](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jwiedenheft/32/32521_2.png) [@jwiedenheft](https://community.hubspot.com/u/jwiedenheft)\
**Post date:** [June 4, 2018, 8:07pm UTC](https://community.hubspot.com/t/sending-emails-via-workflow-with-variable-text/1322/7 "2018-06-04T20:07:34Z")

</div>

Looking to do the same thing with one of our email templates. We noticed the one-line issue, instead of the text being multi-line as denoted by the hard returns.

Here’s what HubSpot Support said when I asked them about the problem:

_Personalization tokens don’t yet have the ability to carry all formatting over from multi-line properties and will often not look the same as if they were entered manually. This is something that our team is working to update, as a lot of our customers are using this method to insert blocks of personalized text in emails, but there is no road map for this just yet. I’m happy to pass along some feedback to my team on this to help push the idea, but I would recommend [creating a post on Hubspot’s Ideas Forum,](https://community.hubspot.com/t5/custom/page/page-id/ideaslandingpage) as it goes right to our developers to show demand and help them decide what feature to implement next!_
