Yeah… this is one of Bubble’s biggest limitations…
Although you can work with Custom JavaScript in Bubble (in various ways, including the toolbox plugin), there’s literally no way you can access or use the output data (unless it’s primitive datatypes, or existing Bubble objects) in the Bubble editor…
Except, that is, by outputting that data as a JSON string, and then sending that string, via the API connector, to a backend workflow in your app, only to return it to the page where it was created, whereby it can then be parsed (thanks to the API Connector) into useable data (API data), that can then be accessed in the editor (ridiculous… yes).
So, you’re forced to incur WU cost, and use server bandwidth, just to access basic data (data that should be entirely client-side).
But… that’s just the way it is with Bubble.
So if you need to work with custom JS and non-Bubble objects, this is the way it has to be done.
(It’s actually not that bad… just a bit frustrating that it has to be this way, just to do super simple things like display some object data on a page).