Hey @emperorrobert! Welcome to the forums!
So the reason you can’t do this here is because it would negate the purpose of the “Location” part of “Location or Actor.” The filter class wouldn’t be able to function at all vs Locations as a location can’t have a class, it’s just a set of 3 floats.
So, I would use a branch. Check if the goal is a vector or an actor. Don’t forget you can just get the location of an actor.
If you need to filter actors, use an Actor based node.
If you need a location, use the Location based node.
It can’t have both a Filter class AND Location reading on the same node because it would pull an error trying to find the class of the location (which doesn’t make sense). Instead of trying to cram all functionality into a single node, just try to figure out how to do it with multiple nodes (then turn that into a function! 
).
I hope that helps you figure out what to do!