My understanding is that the state is managed internally by weweb and is not automatically switched when you focus the input, like what happens for hover state.
For a “onfocus” workflow trigger to manage focus events you need to ask the weweb team.
If you use the workaround that I describe here you can activate your element state by binding the state condition.
In that example you keep track of the focused element updating a variable with the name of the element (the one in the settings panel), so you can bind the focus condition to that.
Something like this:
