----------------------------- **While I generate an answer, here are some sources that might be helpful**: * [Glossary]() * [Server URLs]() * [Server Events]() * [Web SDK]() -----------------------------

### Answer It sounds like you're experiencing issues with the data flow from the webhooks to the next module in Make.com. Since this involves how webhooks from Vapi are interacting with external platforms like Make.com, setting up or troubleshooting this might require checking a few things: 1. **Verify the Data Sent by Vapi**: Ensure that the data sent by Vapi's webhook is correctly formatted and contains the expected information. You can check the server logs or use tools like Postman to simulate the webhook and see the data being sent. 2. **Check Make.com Configuration**: Make sure that the webhook URL and the data handling in Make.com are correctly set up. This includes ensuring that the data paths in the Make.com scenario are correctly mapped from the incoming webhook to the Gmail module. 3. **Debugging**: Check if there are any errors in the logs of Make.com that could give clues as to why the data is not being passed correctly. Sometimes, it could be due to format mismatches or data parsing issues. If the problem persists, you may need to consult the documentation or support for both Vapi and Make.com to resolve the integration issue. Unfortunately, without more specific details on the webhook data and the configuration in Make.com, I can only provide general advice. For more detailed assistance on Vapi's webhook configurations, you can refer to the official documentation on server URLs and events [(1)]() , [(2)]() . This provides comprehensive guidance on how to set up and manage data through webhooks in Vapi.