Is your feature request related to a problem? Please describe.
Two related problems:
If a user wants to publish to both Google sheets and Spool they must currently include and configure both publish platforms on their device, increasing the complexity of the setup, the size of the device code, and the amount of time spent uploading data.
If a user/developer wants to publish data to somewhere that isn't Google sheets or Spool (for example, a different visualization/data analytics tool), they would need to write a new Loom publishing platform. Writing embedded publishing platforms is time-consuming and can be frustrating to test. Additionally, other data publishing locations may or may not even provide a particularly secure interface (SSL, device authentication, etc.).
Describe the solution you'd like
Within Spool, users should be able to add publishing "addons" or "hooks" to their devices/networks which takes all device data received by Spool, repackages it, and sends it to another service (e.g. Google sheets or a more sophisticated data analytics tool). Developers would still need to implement an addon in Spool to handle the data packaging and sending for each service.
Is your feature request related to a problem? Please describe. Two related problems:
Describe the solution you'd like Within Spool, users should be able to add publishing "addons" or "hooks" to their devices/networks which takes all device data received by Spool, repackages it, and sends it to another service (e.g. Google sheets or a more sophisticated data analytics tool). Developers would still need to implement an addon in Spool to handle the data packaging and sending for each service.
Describe alternatives you've considered
Additional context