My team and I encountered a few technical issues when trying to test scenarios on make.com. We are new to vapi and we assume that there is a problem with the structured data. I'm attaching a call ID for reference, 5c2a69a5-dffd-4b54-bb29-3b0809f8df92. Let me know if there is anything else I can provide to help you understand it better.

@AI scale & grow Thank you for reaching out, and I'm here to help! To better assist you with the technical issues you're facing on make.com related to VAPI, could you please provide more details about the structured data problem you're encountering? Specifically, what kind of errors or unexpected behavior are you observing when testing scenarios? Any additional information you can provide will help me understand the issue more clearly and guide you towards a resolution.

@Vapi , basically we can see that the call was recorded and added to the log, but we don't get any data (i.e. it says data: N/A). When integrating with make.com for example, the data is not being sent to the module in our Make scenario. Also, when running the scenario it won't load, and we are assuming that it's because it its not receiving the data. Thanks in advance for your help.

@AI scale & grow I understand the issue now. It seems like there might be a problem with the data payload being sent from VAPI to your Make scenario, which is why you're seeing "data: N/A" and experiencing loading issues. Here are a few steps you can take to troubleshoot this problem: 1. **Check Payload Format**: Ensure that the data payload format expected by Make.com is correctly configured in VAPI. The structure and data types must match what Make.com is expecting to receive. 2. **Review Event Configuration**: Verify that the call events are configured correctly to trigger the Make scenario. This includes checking that the correct events are being captured and sent. 3. **Inspect Logs**: Look at the logs on both VAPI and Make.com to see if there are any error messages or warnings that could indicate where the problem lies. 4. **Test with Static Data**: Try sending a static data payload from VAPI to Make.com to see if the scenario runs successfully with known good data. 5. **Check Make.com Scenario Settings**: Ensure that the Make.com scenario is active and correctly set up to receive data from VAPI. 6. **Network Issues**: Sometimes, network issues or firewalls can block the data from being sent or received. Check to make sure there are no such barriers. If after these steps the issue still persists, please provide any error messages or logs you have, and I'll be happy to assist you further. If you need more detailed support, you can also reach out to the support teams of VAPI or Make.com for assistance.

@Vapi I don't think that the problem is related to Make, as we are seeing the problem on Vapi that the data is not recorded after a call (i.e. even without bringing make into the picture). How can I make the data structure available on Vapi?

@AI scale & grow If the issue is with VAPI not recording the data after a call, it's important to ensure that the data structure is properly defined and that VAPI is configured to capture and store the call data. Here's what you can do to address this: 1. **Review VAPI Configuration**: Go back to the VAPI configuration settings and ensure that you have set up the data structure correctly according to the documentation. This includes defining the data you want to capture from calls. 2. **Check Call Event Handlers**: Make sure that the event handlers for call events (such as call start, call end, etc.) are properly implemented and are designed to capture the necessary data. 3. **Verify Data Storage**: Confirm that VAPI is configured to store the data after a call. This might involve setting up a database or specifying a storage method in your VAPI settings. 4. **Test with Sample Data**: Try initiating a test call and manually inputting sample data to see if it gets recorded. This can help you identify if the issue is with the data capture process or the data itself. 5. **Consult Documentation**: Refer to the VAPI documentation for specific instructions on how to define and capture structured data during and after calls. 6. **Check for Errors**: Look for any error messages in the VAPI logs that might indicate why the data is not being recorded. If you've gone through these steps and the problem persists, it may be necessary to reach out to VAPI support for further assistance. They may need to look into your specific setup and provide more targeted help.

@AI scale & grow could you share: - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help me figure out what went wrong!