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

### Answer It sounds like you are experiencing issues with receiving data in your webhook through function calls. To address this, let's ensure a few things are correctly set up: 1. **Correct Server URL Configuration**: Ensure that your server URL is correctly configured in Vapi to receive function calls. The server URL needs to be a publicly accessible URL pointing to your endpoint. Check the server URL setup in your Vapi dashboard and make sure it's correctly pointing to your Node.js server or make.com webhook [(1)]() . 2. **Server URL Events**: Verify that your server is properly handling the specific type of event that Vapi sends when function calls are made. This includes checking how your server handles

function-call

events. You need to ensure that your server is set up to listen and respond to these POST requests from Vapi [(2)]() . 3. **Function Call Configuration in Vapi**: Make sure that the function you are trying to call is properly defined in your Vapi assistant's configuration. Check if the function is correctly set up with the necessary parameters and that it is enabled in your assistant settings [(3)]() . 4. **Inspecting Logs**: If possible, review the logs from your webhook or Node.js server to see if there are any incoming requests from Vapi when the function call is supposed to trigger. This can provide insights into whether the requests are reaching your server or not. 5. **Testing Endpoint Independently**: Try testing your endpoint directly (e.g., using tools like Postman) to ensure that it can receive and respond to requests, independent of Vapi. This can help isolate the problem whether it's with the endpoint itself or the integration with Vapi. If after checking these areas the issue still persists, you may need to

review the detailed configuration of your function calls and server URL events setup in the Vapi dashboard or seek further specific insights from the function call logs. Ensure that all server responses are correctly formatted as JSON and check for any errors in the request handling logic on your server. For more detailed guidance on setting up and troubleshooting function calls and server URLs, refer to the Vapi documentation on [Function Calling]()and [Server URLs]() [(1)]() .

702e613e-2c12-4240-b683-16c21f9ba3e5

fa39bd93-cbf8-4ced-9fbe-c26c03acec1c

cb1f8b68-dfa3-4996-a9af-6f1318b38daf

95 % cases , i dont get any hit in make.com , and in our custom webhook the failure is 100 %

on your log we found : 20:19:43:048 [ERROR] Server URL Error: Request failed with status code 403

where as, we found all the webhooks are perfectly running

The request was being sent but due to your firewall it was blocked.

Sent you the response data from your server in DM

i can give you the webhook, you can reach the webhook from anywhere, no firewall at all