An Input Action is a logical representation of something the user can do, such as "Jump" or "Crouch". These are what your gameplay code binds to in order to listen for input state changes. For most scenarios your gameplay code should be listening for the "Triggered" event on an input action. This will allow for the most scalable and customizable input configuration because you can add different triggers for each key mapping in the Input Mapping Context.