tool-call response
# support
m
Hey guys, I am having an issue getting beck the response when calling a tool. The server is on Make. Here is my webhook response format:{ "results": [ { "toolCallId": "toolCallId", "result": "result" } ] }. I also made sure that it is in JSON format by adding a header "Content-Type application/json" but it still doesn't work. Vapi assistant waits for the response but when I check the response on the call logs, that is what I get: No result returned. Does anyone know what I'm doing wrong?
v
message has been deleted
@Mzst Hello! It sounds like you've set up your webhook response correctly with the JSON format and the appropriate
Content-Type
header. However, if VAPI is not receiving the expected results, there might be a few areas to check: 1. **Payload Structure**: Ensure that the actual payload you're sending matches the expected structure exactly. The
toolCallId
and
result
fields should contain the actual values rather than the placeholder strings
"toolCallId"
and
"result"
. 2. **Server Processing**: Verify that your server on Make is correctly processing the incoming request and that the logic to generate the response is functioning as intended. 3. **Network Issues**: There could be network issues preventing the response from reaching VAPI. Check for any errors in the network logs. 4. **Correct Endpoint**: Make sure that the endpoint URL configured in VAPI is correct and that it points to the right server on Make. 5. **HTTP Status Codes**: Ensure that your server is sending back an HTTP 200 OK status code along with the JSON response. Any other status code might cause VAPI to interpret the response as an error. If you've checked all these areas and the issue persists, it might be helpful to provide more specific details about the configuration or logs from your server on Make. This way, we can assist you more effectively. If you need further assistance, please don't hesitate to ask.
You can continue this conversation by mentioning me in the message.
s
can you provide latest call_id?
s
because of no response closing this ticket.
3 Views