Playmaker comes with a huge amount of "Actions". The majority of those Actions are very generic in purpose, allowing you to do simple things on a variety of objects, variables and scripts and then build from there to make huge, complex machines doing whatever you want very specifically. You can use some Actions to manipulate other scripts you've downloaded from the asset store and there are also the Get Property and Set Property actions which are extremely versatile in reaching into any scripted component and giving you a very simple list of variables to manipulate.
This is all completely useless if the end user does not take advantage of it. The point of playmaker is allowing someone to use these actions to create state machines that "do" things, and being how generic most of those actions are, the limit of capability for the asset is actually pretty hard to reach. The answer to your question is yes, you could do this with playmaker without touching a script. Is that the best way? Maybe not, a coder could make this just as easily, I'm sure.
Playmaker can be used as a coder's accessory, doing some things faster while he may prefer to code a majority of his work. On the other hand some people - myself included - will do everything in playmaker, using no outside scripts. If I really need something custom due to the lack of coding knowledge I might just go and make a custom action to do it for me and move forward with that since they're pretty easy most of the time.
I hope this clarifies. Playmaker isn't one of those assets you buy and then have buyer's remorse about for weeks to come, its a hugely capable tool limited only by the end users ability to find ways to develop within it and those end users come from a wide variety of backgrounds and use Playmaker for very different things.
