Good to hear from you! Yes, I am quite familiar with the API tool. I’ve been using it a lot! In this case, the JSON would not be coming from an API call. I am thinking about the data integration possibilities of Wappler, in particular, consuming output from other scripts/services that may be running on the server. For example, if I could have ServerConnect to Import a JSON File (which may be triggered by the Action Scheduler) I could do a lot more with connecting Wappler to other services/scripts that don’t have a web services API for me to query but do have a valid JSON output that can be worked with further (visualized, processed, emailed, etc.).
I think this would extend Wappler’s integrations capabilities even more while leveraging some of the existing technology (importing files and JSON parsing).