My workflow stopped working. I have a workflo...

(Aaron Moolb) #1

My workflow stopped working. I have a workflow with an email body to show a bunch of inof including an image column. It was working great. Now the image column just shows the URL in the email body instead of the image. Any ideas?

(Aleksi Alkio) #2

Is it possible that you have removed the image or changed the position?

(Aaron Moolb) #3

Nope, it was working great and then I ran the workflow today and now its not.

The URLs in the email are good and when I click on them, they go to the image.

(Praveen Seshadri (AppSheet)) #4

Please check the image column. Is the type still image or is it Url? If it is Image, then it will show as an inline image in the email

(Aaron Moolb) #5

Its still image with no luck Ive checked all of my image columns in all tables and none are URL

(Philip Garrett) #6


This problem is the result of a change I made late last week.

For workflows, we previously always formatted images, files, and URLs as HREFs. We did this regardless of the target template type.

Another customer reported that doing this for the JSON body of a Webhook makes no sense. He asked that we simply format the image as a URL when it appears in the JSON body of a Webhook.

I made that change late last week. We now decide whether to format the image as an HREF or as a URL based on the target template type. If the template type is HTML, we format the image as an HREF. If the target template type is JSON or Text, we format the image as a URL. That approach appears to work well.

Your workflow is doing something I did not consider. You are entering HTML directly into the “Email Body” property. But since the “Email Body” is treated as text, we format the image field as a URL.

There are two things you can do to resolve the problem.

  1. The easiest is to construct the HREF in your “Email Body” by replacing

<<[Product Image]>>


<a href=<<[Product Image]>> ><img src=<<[Product Image]>> />

That is consistent with your current approach of hand constructing the HTML markup in the “Email Body”.

  1. The other approach would be to replace your “Body Template” with an equivalent “Email Body Template” written in either Google Docs or Microsoft Word. In that case, the target template type is HTML and we would automatically construct the HREF for the image file.

I investigated whether I could recognize what you are doing as a special case and add extra code to handle it. I spent a couple of hours trying this, but I am having trouble finding a solution that works reliably.

Can you use one of the two approaches I describe above? That will get your app up and running quickly. I think the first approach would be easier for you.

If lots of customers run into this, I may need to spend more time to try to find a way to handle it automatically. I am hoping that this is a rare case and I can avoid doing that.

(Aaron Moolb) #7

Thanks for looking into this. I will continue to utilize HTML and use the <a href=<<[Product Image]>> ><img src=<<[Product Image]>> /> You suggested. I will post again should something not work properly.

(Philip Garrett) #8


Thanks Aaron.