Unfortunatly, There is no easy way out of this, touch screen management and api was done in such a way that it's something totally different and incompatible with the current input system of Unity... This is a real shame, and actually I think a big mistake, maybe they are planning on making a better input manager but I doubt it very much... I guess every "serious" project are rolling there own input system. Even I on my first project has to create my own input manager to work on top of all this mess...
The problems boils down to the fact that existing controllers relies on the fact that the developer is using the scripting environment, and for this everything is just working fine, but because playmaker is a visual development environment, it makes it then very difficult for using existing controllers.
The solutions are to either
1: build your controller in playmaker. This is fine, but do require that extra effort ( when you know that a controller is sitting here with everything you need...)
2: build a bridge to make that controller accessible from playmaker environment, that is either create actions, or proxies ( more on this if you need examples, just shout, and I'll give more details)
3: Have you studied the various samples, videos and screencast on the topic. Surely, you will find enough materials to build your own controller all in PlayMaker