AFAIK, this is not a feature available in nanoflows yet.
You would have to build separate nanoflows per button and use a common sub nanoflow to actually to the task. That way, you can pass a string parameter (perhaps it's class name or any identifier) to the common sub nanoflow per button and use it.