Skip to main content

  1. Describe the problem your experiencing and how your idea helps solve this


Currently, Figma only allows to select one action for a trigger in prototyping. This means that when applying e.g. an “On Click” trigger to an element, it’s not possible to have multiple actions (like showing two overlays) when the element is clicked. By allowing to add multiple actions to a trigger, prototyping would get much more powerful and useful!



  1. Add as much context as possible (screenshots, Figma files, mockups, etc.)


I faced this issue when I wanted to show a notification that automatically appears and disappears after using a specific action (e.g. create, delete an element).


Screen Shot 2021-05-14 at 12.00.47


Currently, you would have to build many screens to imitate this behaviour. If multiple actions would be allowed, it would be much simpler and efficient to create such flows. In my example, it would be set up like this:

Show an overlay on click → delay → show another overlay → delay → close the overlay



  1. Ask questions to bring the community into the conversation

    (e.g. Does anyone else experience this? Is anyone using a plugin or workaround to help solve this?, etc.


I assume that there are also multiple other use cases when more actions are needed for a single trigger on an element. It would be awesome if somebody who stumbled across this issue would describe their use cases as well!

Come on Figma! Please add this feature

I share your frustration @Laura_Bergmann; I’m creating an anchor dock in Figma that has hover and click interactions. The interactions work well on their own, but when I integrated the dock onto my page and added anchor links, two of the four previous interactions (hover and click) were ignored.

Hello. I’m new to Figma and UI/UX Design and also bumped into a brick wall in my first practice project. I need multiple actions to kick in after a single click event but this seems impossible at present. Please if there’s a workaround, I’d really appreciate it thanks

I’d really prefer to stay in Figma when prototyping rather than exporting to Origami/Protopie. The radio silence is pretty weird here.

You can use hover, click, and press at the same time which helps. Click can navigate to next screen and hover and press can change the button states.

@Steven_J_Vasilakis sure, but what if you want a click to change a toggle state and spawn a toast?

So… I am using “Click” and “While Pressed” to basically perform 2 actions at once. While pressed changes the variant, and click opens the overlay for example. I agree though I would also like to see multiple actions supported per any specific interaction.

I ran into this within about 15 minutes as well—this is a must have. In general it’s surprising that an event can’t simply change the state/variant of an arbitrary number of other objects.


The terrible workaround I’ve found is to group together the objects that need to be changed and cram the combined changes into variants, but this gets unwieldy very quickly.


Overhauling this would multiply the power of Figma many times over!

This is needed asap! #ProtoPie was better

Have you tried on ‘Touch Down & Touch Up’ to change your button state and open your overlay nearly simultaneously instead of just on ‘Tap’ or ‘Click’? It will feel almost instantaneous to a user unless they click and hold or long press. Here is an example using a copy of the other file on this thread, but using the on ‘Touch Down & Touch Up’ method to do multiple things at once. Here is the link to the build file for my iteration. You will need the latest Roboto and Roboto Condensed Font Families for the fonts and icons to render properly. I created both a button state and toggle state change sample with concurrent overlay interactions in the examples above. Long Pressing or Mousing Down/Clicking and Holding will break this experience obviously, but I believe this can solve what you are striving to do.


Hope this helps!

I also ran into this issue while trying to make a todo list app with checkboxes and unselect all selected option. I couldn’t get the functionality of the unselect button. Additionally, I wanted the check boxes to impact two new states which I could only do when I duplicated the whole list and made changes to the states I wanted impacted. However, it was not practical to make all of the possible combinations of selected items.

I believe that adding such a necessary feature for prototyping is a sign of respect for users. It’s disappointing to hear that Figma hasn’t implemented this feature yet, despite it being requested since 2021. It’s especially frustrating considering that Axure has had this feature for a long time now. God, what a disrespect for users.

This is an almost perfect Workaround! Thanks a lot!

Just adding a big +1 for this feature. Figma, you have a great reputation for getting needed features out quickly! Would love to see this one soon.

Figma team, please add the multiple interactions on one click feature.

Please add this feature, I want to be able to do this with Video components:

on click =: play/pause AND open an overlay

I second this, I wanted to have a radial button to select ‘delivery’, which selected on click but also shows the delivery price… I’m sure there are many usages for multiple actions on click! 🙂

Unfortunately the Problem with this solution is, that with “Click” you seem to set a “sticky” Component-State, which isn’t set with the “touch up & down” approach.


I am trying to build an interface in which a user can add an item to a list. This action triggers a Button-State from “add item” to “item added” while a Layer (toast) appears, which tells the user that the item was added to their list.


This works with your approach, but every time the User re-enters the page, the Button-State is resetted. 😩

Why can’t I stack a click and hover interaction on the same component?


It always says “This interaction will not be triggered as another one will be triggered first”. And even if I change the order of the interactions it doesn’t make a difference. I can’t get both to exist at the same time. Why even allow me to +add an interaction if they won’t stack?


Use Case:



  1. Have a button that changes color while you hover over it.

  2. If button is clicked on, add an overlay.

  3. Or if button is clicked on navigate to a new screen. (where the overlay exists)


omg I’m so frustrated. 🤦🏼‍♂️

This should work:



  1. Build a component containing the desired button-states.

  2. add the hover-Interactions inside the component (change to)

  3. Add the component to the artboard, assign the click event to the button.

Yes please

I too, would very much appreciate this feature. I’ve been trying to design a save button interaction on a component that once clicked should change to a different state and also show a small feedback notification overlay that simply says “Saved”.


I’ve gotten around it by adding another click event on the next component state to open the overlay. This work okay when I’m recording a screencast of a prototype but it doesn’t work when having someone else click through it as that wouldn’t normally be required.

WT Actual F @Figma_Support How is this not a thing yet? It has been 2 eFFing years.

We hear you and understand your frustration. The prototyping team is aware of this feature request and we hope to be able to provide a clear roadmap in the future.


The community team here will continue to pass along feedback and measure overall interest through Votes. This is definitely near the top voted, but to be completely transparent, there’s still ~10 other features with more Votes that are being prioritized by our developers.

i’d be interested to know what the other top rated vote getters are at this point.

Terms & ConditionsCookie settings