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

### Answer It sounds like there might be an issue with how the webhook is set up or being triggered from Vapi's side. If the webhook worked initially but stopped after changes were made, it's essential to ensure the payload or the function calling criteria hasn't been altered in a way that prevents the webhook from firing. 1. Check the Server URL Configuration: Verify the server URL is correctly set up in Vapi to point to your Make.com webhook. You can refer to the setup guide for server URLs to ensure everything is configured properly [(1)]() . 2. Review the Function Calls: Ensure that the function calls are properly defined and that they match the expected parameters from Make.com. Misconfiguration here could lead to empty parameters or no data being sent . 3. Debugging Tips: - Check Logs: Look at the logs in Vapi's dashboard if available, to see if there's an indication of what might be going wrong. - Test with Static Data: Temporarily hardcode some test data in your Vapi function call to see if the issue is with the data generation or the webhook call itself. 4. Webhook Settings on Make.com: Double-check if there are any settings on Make.com that might be filtering out incoming calls from Vapi based on certain conditions. If you've gone through these steps and still face issues, it might be beneficial to revisit the changes made in Vapi after the first successful attempt and incrementally apply changes to isolate the issue.

Another update: I realized I need to have Function Call in Server Messages, but the Parameters are still empty on test

Glad I could be helpful. Feel free to create a new thread with any new questions you may have.