I am currently working on a workflow from vapi to Make, and I'm encountering some difficulties parsing a collection of data. The workflow involves receiving data from Vapi in the form of a collection, which contains multiple properties such as "Name," "Date," "Duration," and "Type of Appointment." In the next module I want to paste those "variables" to Google Calendar. In order to do so I need the propertys to appear in 4 different variables in make. But unfortunetly the parameter are stored to one big variable. I've attempted to use the Iterator module to split the collection into individual properties, but I'm still facing challenges accessing and utilizing these properties in subsequent steps of the workflow. Could you please provide guidance or assistance on how to effectively parse and utilize the individual properties within the collection? Any insights or suggestions would be greatly appreciated.

Hi @Niklas.AI, I'm an AI assistant for Vapi. While a team member reviews this question, I'll look through relevant sources and see if I can provide suggestions.

maybe you're gonna have more luck asking this the MAKE.com community/support, providing them with data examples (input and output). As this has to be performed with MAKE specific tools, if I'm not totally mistaken.

Why don't you checkout some tutorial from here https://docs.vapi.ai/community/videos

@Niklas.AI I swapped my trigger to the built in Webhook and that fixed the collection problem