I can see where you want to go with this, but there are some limitations in the plugin mechanism that get in the way.
The plugin can return these objects, if the plugin has the objects are passed in. It cannot modify them or create new ones, but it can however arrange them in a list.
When you setup the API connector, you can choose it to parse the JSON, for which it creates its own types and are kind of inflexible but can be used by Bubble’s expressions.
The results from the APIs in the plugin are not sent to anywhere else in the plugin, that would need to be done by the app developer.
Some options here:
- The app developer passes the data field by field into workflow steps like Create a thing.
- The plugin returns JSON text and its stored as text, with all the associated problems like not being searchable etc.
I suggest that the implementation you are thinking of is impractical, so try looking at the problem a different way and come up with a different solution.