@Simon J.
I'm sorry to hear you're experiencing issues with the integration between VAPI and Make.com. It seems like you've already taken several important troubleshooting steps. Since the issue persists, I would recommend checking a few more things:
1. **Data Format and Payload**: Ensure that the data being sent from VAPI to Make.com is in the correct format expected by Make.com. The payload must match the structure that Make.com is configured to parse.
2. **Webhooks Configuration**: Double-check that the webhooks in Make.com are set to "re-determine data structure" after you've sent the new calls. Sometimes, webhooks need to be triggered with the correct data to update the structure.
3. **API Logs**: Review the logs on both VAPI and Make.com to see if there are any errors or messages that could indicate where the problem lies.
4. **Network Issues**: Verify there are no network issues that could be preventing the data from being transmitted correctly.
5. **Compatibility**: Check if there have been any updates either on VAPI or Make.com that could affect compatibility.
6. **Support Channels**: If the issue is still unresolved, consider reaching out to the support teams of both VAPI and Make.com for more specialized assistance.
If you need further assistance with specific VAPI functions or actions, please let me know, and I'll be happy to help. If the problem is on the Make.com side, it might be best to contact their support for more detailed guidance.