It’s not obvious, but that information is available in the smartthings system, it’s just not readily exposed through the mobile app UI.
So to get that information, many people use the virtual switch method which @Automated_House mentioned.
The point is that smartthings does allow a routine to turn a virtual Switch on/off and also allows you to set a routine to be automatically fired whenever A virtual switch is turned on/off.
So anything which a routine can do can be initiated by a switch.
That gives you very simple integration with many third-party systems including IFTTT, Amazon echo, etc. They can’t see the SmartThings modes, alarm states, door unlock routines, etc-- but they can see a simple switch, and you can set it up so that that switch going on or off will cause any of the other things to happen on the SmartThings side.
Here is the FAQ for that (this is a clickable link)
So that’s the good news. Pretty much anything that smart things can do can be controlled through its IFTTT channel by using the virtual switch method described in the FAQ.
Unfortunately, the bad news is that doesn’t help in this particular case, because Kevo does not allow its lock to be a “that” in an IFTTT applet. So no matter what the SmartThings event is, you can’t use the Kevo IFTTT channel to unlock the lock because of restrictions on the Kevo side.