# Newbie Event Question

**URL:** <https://community.weweb.io/t/newbie-event-question/17941>\
**Category:** How do I?\
**Created:** [April 25, 2025, 12:19am UTC](https://community.weweb.io/t/newbie-event-question/17941 "2025-04-25T00:19:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![przemek](https://avatars.discourse-cdn.com/v4/letter/p/96bed5/32.png) [@przemek](https://community.weweb.io/u/przemek)\
**Post date:** [April 25, 2025, 12:19am UTC](https://community.weweb.io/t/newbie-event-question/17941/1 "2025-04-25T00:19:42Z")

</div>

I have a button and when I click it I want a modal to pop up. My understanding is that there should be a onClick trigger on a button that I can wire up to execute a workflow: my worflow would do whatever is necessary to show the modal.

The problem is that I cannot find anything on my button that allows me to wire up the onClick?

---

<div class="post-metadata">

**Author:** ![sam1](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/sam1/32/6724_2.png) [@sam1](https://community.weweb.io/u/sam1)\
**Post date:** [April 25, 2025, 1:00am UTC](https://community.weweb.io/t/newbie-event-question/17941/2 "2025-04-25T01:00:47Z")

</div>

When you click the element the far right tab in the editor is for workflows add on and you can select what it’s for on click ECT. Take a look at the weweb academy good place to learn some of the basics like this.

---

<div class="post-metadata">

**Author:** ![przemek](https://avatars.discourse-cdn.com/v4/letter/p/96bed5/32.png) [@przemek](https://community.weweb.io/u/przemek)\
**Post date:** [April 25, 2025, 1:23am UTC](https://community.weweb.io/t/newbie-event-question/17941/3 "2025-04-25T01:23:39Z")

</div>

So I select my button and on the right workflow tab I click “New”. When I do that nothing happens.

In the console I can see an error when I press “New”:

TypeError: undefined is not an object (evaluating ‘this.triggerOptions.find’)  
addWorkflow — index.c4bca102.js:1264:174082  
d — chunk-vendors.052158eb.js:381:1465  
h — chunk-vendors.052158eb.js:381:1540  
en — chunk-vendors.052158eb.js:383:30330  
d — chunk-vendors.052158eb.js:381:1465  
h — chunk-vendors.052158eb.js:381:1540  
i — chunk-vendors.052158eb.js:118:8694

 ![Screenshot 2025-04-24 at 18.21.48](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/e/e663e0c8f0a34b45f251e7ca7227dfde2f3d620b.jpeg)

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [April 25, 2025, 9:00am UTC](https://community.weweb.io/t/newbie-event-question/17941/4 "2025-04-25T09:00:49Z")

</div>

Create a ticket at [support.weweb.io](http://support.weweb.io)

---

<div class="post-metadata">

**Author:** ![przemek](https://avatars.discourse-cdn.com/v4/letter/p/96bed5/32.png) [@przemek](https://community.weweb.io/u/przemek)\
**Post date:** [April 25, 2025, 5:03pm UTC](https://community.weweb.io/t/newbie-event-question/17941/5 "2025-04-25T17:03:26Z")

</div>

Yep I created a ticket.

Turns out this is a bug in Safari and Firefox. Weweb works correctly in Chrome and Opera.

So for anyone having the same issue use Chrome or Opera until they fix this.