Parse JSON from API Call (without JavaScript)

I’m building a PoC and have some pretty in-depth JSON response data that I am seeking to parse into columns. Arrays within arrays within arrays. Paginated data.

I am wondering if this is has changed with recent improvement/change-over to workflows. I searched around and haven’t see anything very recent (other than a November 2024 feature request) about an ability to quickly/easily parse JSON into columns without writing JavaScript.

I fear that I’ve been spoiled and become lazy due to Make.com making this so easy to do.

Use a Query JSON column.

1 Like

Thanks @Darren_Murphy! I guess I was searching poorly and/or with the wrong strings.

Warning to others: I’m immediately noticing that docs are a little bit out of date (they’ve moved JSON Object under the Data menu instead of Integration menu) but otherwise good.

Now, to see what I can do with the workflows to take a large this daily JSON request that could be summarized as an array of users and their logins and break it columns and into row data.

I’m hoping that this is going to be as simple as Call API > JSON Object(s) >Data - New Row

This JSON package received from the API endpoint could be summarized as an array of users and subarray of their logins. It’s much more complicated/detailed than that but the jist of it this is converting that to Glide table(s) for analysis and alerting.

Just following up on my outcome here…

This use-case just seems to exceed what Glide’s great at. Totally achievable in Glide - but at a steep complexity. Glide is AWESOME so don’t get the wrong impression from the following.

This was going to take mind-bending complexity to iterate this data set and its sister dataset into columns and rows within Glide. Inversely this was accomplished in minutes with a Make.com scenario using just a few modules: Repeater and set/get variables (for the pagination), an API request to the foreign system with the output into an iterator module and that iterated data into the Glide API module. The step that took the longest was defining the fields and mapping the data to the fields.

Is this more expensive in dollars/currency over the long-run? Yes.
Is it more complex? No, each platform is doing what it’s great at.

HUGE progress has been made in Glide and the new workflows feature is great but Make.com (which also has some of its own challenges) remains the standard for me with this type of thing.

I have to agree with this. I can think of how to deal with this in Make.com, but with Glide it’s a bit more complex at the moment. I believe they will get there though. Workflows is great and has solved many of my problems.

1 Like

100% agree.

1 Like