\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [March 13, 2018, 9:04pm UTC](https://discuss.elastic.co/t/html-field-for-email/123809 "2018-03-13T21:04:38Z")\
**Posts on this page:** 4\
**Page:** 1
**Author:**  [@Pororo](https://discuss.elastic.co/u/Pororo)\
**Post date:** [March 13, 2018, 9:04pm UTC](https://discuss.elastic.co/t/html-field-for-email/123809/1 "2018-03-13T21:04:39Z")
I was trying to set the html for the email alerting in watcher. What I did is to copy and paste my html code into the body.html field. But it caused some indent problems that the system could not recognize it is a valid html. So I just typed my html code into one whole long line at that filed and it worked fine for some simple html. When it was involved some complicated situations like img url or something like that. One whole long line of html code still cause the invalid warning. Is there any way to efficiently input the html code to that field?
---
**Author:**  [@Bill\_McConaghy](https://discuss.elastic.co/u/Bill_McConaghy)\
**Post date:** [March 15, 2018, 7:59pm UTC](https://discuss.elastic.co/t/html-field-for-email/123809/2 "2018-03-15T19:59:44Z")
I suspect that the issue with img tags had to do with the quotation marks around src="...", etc. Did you try escaping those? (\
**Author:**  [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [March 15, 2018, 8:48pm UTC](https://discuss.elastic.co/t/html-field-for-email/123809/3 "2018-03-15T20:48:45Z")
You might be able to change the HTML sanitizer allow/deny settings to be able to write the HTML you want. See [https://www.elastic.co/guide/en/x-pack/6.2/actions-email.html#email-html-sanitization](https://www.elastic.co/guide/en/x-pack/6.2/actions-email.html#email-html-sanitization)
---
**Author:**  [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 12, 2018, 8:48pm UTC](https://discuss.elastic.co/t/html-field-for-email/123809/4 "2018-04-12T20:48:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.