Nov 19, 2024 09:48 PM
Hi,
We're working on moving automation mail (Gmail) content from the automations themselves to a separate table, where other than admins can maintain text.
In the mail content there may be markdown URLs with clickable "friendly names", e.g. [Book here](https://www.calendly.com). I copied the whole text from the automation to "Long text" fields with rich formatting enabled. This approach doesn't however produce markdown URLs, instead they print out the raw markdown syntax ('[Book here](https://www.calendly.com)').
Remembering that using CONCATENATE formulas for URLs works in achieving the "friendly names" I tried chopping up the mail content, and using a summarising CONCATENATE field as input for the automation instead of a Long text field. This works, producing "friendly name" clickable URLs.
However, we have URLs in various places in the content, so chopping these up becomes really tedious, if not impossible. A workaround is to have body content first with text telling the reader something like "you'll find the links at the end of this mail", but that is just confusing and plain bad UX.
Isn't there really a way for an automation to produce marked down URL direct from a Long text field? Or some other workaround..?
Rgds,
Björn
Solved! Go to Solution.
Nov 20, 2024 04:36 AM - edited Nov 20, 2024 04:36 AM
Did you see my latest post? It works with a long text field, but not when rich text is turned on.
Nov 20, 2024 04:36 AM
I don't see there would be a separate rich text field, only a long text field for which you can enable rich text, like here:
Or do you that I should turn off rich text for the long text field for markdown to work? That would actually make sense, now come to think of it, not having two different layers of formatting at the same time.
Rgds,
Björn
Nov 20, 2024 04:38 AM - edited Nov 20, 2024 04:39 AM
Right, that’s what I’m referring to.
Nov 20, 2024 05:23 AM
OK, thank you. Yes, that makes sense. Very good to have this cleared up :).
Rgds,
Björn