Nov 10, 2022 02:22 PM
Hello! I work for a government office which handles various requests from constituents (water issues, waste management, tree trimming, etc). Our current system uses three tables; one for requests, one for our database of constituents, and one for the types of requests we receive.
When we receive a request, we create a record which describes the issue and link to the person who submitted it as well as to the type of request. Our type of requests (ToRs) contain instructions for how to solve the issue. Our current process has us copying the information from ToRs into an email to the constituent.
My goal is to create an automation which pulls the instructions from the ToR and sends an email to the constituent who created the request. Basically, we review the request and if it doesn’t require any personalization, we could click a checkbox and it would send.
I have the logic setup. The problem is that the information about the ToRs exists in a long-form text field with hyperlinks to city websites. When the automation sends the email, the hyperlinks are removed. We also want these ToR records to be public facing on our website. How can I set it up so that the hyperlinks are maintained when the email pulls from the text field?
Here is what a ToR looks like:
My current automation sends an email with text from a lookup field which reads the long text field. The result removes the hyperlink:
The lookup field removes the hyperlink:
And the resulting email:
Long story short: send text from details field in automated email and keep the hyperlinks.
Thank you!!!
Nov 11, 2022 02:24 PM
Hey Jordan!
You were so close!
What you need to do is format the link in your multi-line field as markdown so in your case it’d be:
[Open Fire Hydrant Complaint](paste your URL here)
Give that a shot!
Nov 11, 2022 03:18 PM
Well I will be darned!! I knew markdown was the way to situate hyperlinks in an automated email, but it doesn’t work in long text fields. The hyperlink does indeed appear when the lookup field is created though. Thanks for the help, I will have to go through our hundreds of requests and create descriptions with markdown versions but it will be worth it!!