Unfortunately, beyond what has been mentioned in this thread already, we currently only support haptics endpoints that can be driven by audio data. You can read more about this here, as well as a potential workaround based on metering information : Feature requests: panning paths, effect presets in mixer, motion plugin, and LPF/spread control in spatializer - #6 by joseph
If you have a specific haptics endpoint that you’re using or have in mind that does allow audio data to drive it, please feel free to let me know, and I will pass it along to the development team for further investigation.