not recognizing my webhook response from query too...
# support
t
Has anyone had success using query tools to call to a n8n Webhook to get a response? In my call log from the AI it shows “no result” but in my webhook it shows the response in clear JSON like this: {“output”: “there was a match”} I know this error cannot be in my prompt, since it gives the AI clear directions. Already have been in a back and forth email with Vapi Support. Anyone had success?
c
To help track down this issue, could you share one or two: \- The call ID This would really help us figure out what went wrong!
t
I found out. Looked through the forms in this discord. The format was wrong.
Copy code
json
{
  "results": [
    {
      "toolCallId": "<the id from the request>",
      "result": "<your message>"
    }
  ]
}
k
How can you elaborate more?
t
When the agent uses a query tool, the following format is needed on responding back to the webhook for the ai voice agent to understand the result or else in call log it’ll show “No result” when query tool is called.
c
Checking if this issue is resolved..
And can you share the correct format..
t
The correct format is this… { "results": [ { "toolCallId": "", "result": "" } ] }
My format when the error was occurring on response back to the webhook was… { “Output”: “” }
c
Hey trev, Kings Big's actually out on an offsite right now, but he'll be able to dive into this for you on Monday, and help figure out the best approach for your setup. Regards, Shubham Bajaj Solutions Engineer
Hey trev, Just a heads-up Kings Big is out for the weekend and will be back on Monday. Once he’s back, he’ll dive into this and help you figure out the best approach for your issue. Regards, Shubham Bajaj Solutions Engineer
Hey trev, Just a heads-up Kings Big is out for the weekend and will be back on Monday. Once he’s back, he’ll dive into this and help you figure out the best approach for your issue. Regards, Shubham Bajaj Solutions Engineer
Hey Trev, Apologies for the same email getting repeated more than once. There is a bug in our system which has triggered this email to be sent again many times. I will make sure that this never gets repeated again.
6 Views