Depending on your coding, it may be possible, but in general, I try to discourage having a bunch of triggers in the same piston. (the lightning bolts in the left margin)
It is not set in stone, but having multiple triggers in a piston can make simple code much more complex to deal with, and harder to troubleshoot. (and a nightmare with schedules)
I usually code each piston with either zero or one trigger, although I will occasionally use two triggers if they are both the same device.
(For clarity, I may use 20 IF statements in that piston, but they are conditions, not triggers)
Personally, when I am trying to stay organized, I use: Dashboard > Settings > Categories…
Beyond that, I name my pistons: Room Name - Function
Since pistons are listed alphabetically within each category.
Just my two cents.