# Trigger a workflow via JavaScript

**URL:** <https://community.weweb.io/t/trigger-a-workflow-via-javascript/929>\
**Category:** Ask us anything\
**Created:** [August 2, 2022, 8:09pm UTC](https://community.weweb.io/t/trigger-a-workflow-via-javascript/929 "2022-08-02T20:09:56Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![dorilama](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/dorilama/32/10403_2.png) [@dorilama](https://community.weweb.io/u/dorilama)\
**Post date:** [August 3, 2022, 2:00pm UTC](https://community.weweb.io/t/trigger-a-workflow-via-javascript/929/9 "2022-08-03T14:00:49Z")

</div>

Standard considerations about security apply, the most critical is: are you inserting user generated content in the html component?  
If yes you should assess if this can be a problem in your specific case.

Here is an example:  
 ![chrome_4EKBR3O0FK](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/6/67ce69f8c1cae579d4ac8e930a1536358caaf661.gif)

A custom plugin instead can avoid this kind of problem.

---

_[View the full topic](https://community.weweb.io/t/trigger-a-workflow-via-javascript/929)._