I’m using GlideApps to automate a series of processes for a company app. I’m basically reading lines off a delivery note. The delivery items—let’s call them pieces of furniture—have multiple lines, which I’m breaking down into JSON. These lines include the product name, dimensions, and materials used.
I’m processing the initial AI reading of the document into a packaged JSON that covers the entire project. Each individual furniture item then has its own JSON format, using the same headings: furniture name, materials, dimensions—nested inside the original JSON payload.
What I’m trying to do now is automate the next step. Once the project is ingested and I’ve queried the JSON, I want another workflow to kick in. This workflow should take the internal JSON payloads and automatically convert them into different lines or rows in Glide, creating separate entries for each furniture piece.
How do I do that?
I think what you want to do here is to get the nested JSON that AI generated, send it in the body in your trigger workflow.
Then in the webhook workflow, loop through the trigger’s body. In each loop, query out the keys from the JSON, and add them to a row in your database.
1 Like
The nested Json comes through in the body of the last trigger, using a manual trigger. Are you suggesting I created a webhook to a webhook trigger?
No, I was asking because your screenshot here shows you’re using an app interaction trigger.
Now seeing your screenshots, I think yes, it would work. When you loop through a JSON like that, does it give you access to the key-value pairs automatically or do you still have to do query JSON steps?
1 Like
It does neither, It doesn’t allow the loop to run at all. Its stops at the project loop, after a successful search.
Does the JSON loop have to be inside the Project loop? I assume it doesn’t? Can you try moving it out?
1 Like
I did this by creating a new json object in the column to the right, and run the loop off that. With no luck.
So in here, if you don’t do the Project loop at all and just loop through the JSON, it still doesn’t work?
1 Like
Still not… refuses to run the Json loop, which it made.
So you send the JSON to the other workflow through this step, then try to loop through it in the new workflow, but it doesn’t work?
Can you attach 2 screenshots of them? I’m running out of suggestions to make at this point.
1 Like
So ultimately, the issue here seems to be none of Proj ID, Comp ID or Json seems to show up in rhe test run for the Manual Trigger? Is that what you imply with the last screenshot?
1 Like
Yes. It refused to run the loop.
Is it possible for you to share an invitation for me to join the team, and tell me how to reproduce the error?
If yes, please send me an invitation link via a personal message in this forum.
