Vapi is no longer handling inbound calls.
# support
s
call id 15f2f036-bf09-4a0e-8de9-63dfb1e36e40 I'm using a Make webhook module to create an assistant for inbound calls. However I get a couldn't get assistant error. My json starts like this:
Copy code
{
  "assistant": {
    "name": "Form Submission",
         "voice": {
        "voiceId":
I tried adding the assistant id to fix it, but this didn't work either:
Copy code
{
"assistantId": "f177bcaf-d97d-4c81-acb4"
  "assistant": {
    "name": "Form Submission",
         "voice": {
        "voiceId":
I need help urgently, customers are giving me rolling eye emoijs.
v
@Sajitsu I'm here to help! It looks like there might be a formatting issue with your JSON configuration. JSON requires proper syntax, including commas to separate fields. Let's correct the JSON structure and ensure that all necessary fields are included. For the assistant configuration, you should have something like this:
Copy code
json
{
  "assistantId": "f177bcaf-d97d-4c81-acb4",
  "assistant": {
    "name": "Form Submission",
    "voice": {
      "voiceId": "your-voice-id-here"
    }
  }
}
Make sure to replace
"your-voice-id-here"
with the actual voice ID you want to use. Also, ensure that the
assistantId
is correct and that it matches the ID provided by the VAPI service. If you've already tried this and it's still not working, it could be an issue with the VAPI service or the way the webhook is set up. In that case, please provide more details about the error message you're receiving, and I'll do my best to assist you further. If the issue persists, you may need to reach out to the support team for more in-depth troubleshooting.
You can continue this conversation by mentioning me in the message.
s
I tried that it still didn't work
@User help please
@Sahil
s
call_id pls
s
call id 15f2f036-bf09-4a0e-8de9-63dfb1e36e40
Did you find anything?
latest call id: ae7db95a-d769-49ad-b3ba-f01fbe14e155
s
Check you phone provider log
There is no error from our side.
s
Oh let me see
My balance is good
I'm looking at the Make log and it shows vapi couldn't get assistant
Twilio log:
Copy code
<Response>
    <Say>Couldn't Get Assistant. Either Set The Assistant I D On The Phone Number. Or, To Debug Your Assistant Request, Check The Debugging Artifacts That Were Just Sent To Your Server.</Say>
</Response>
s
Check your server from where you sending back the response.
You must have received what was the issue with your payload.
s
Copy code
"endedReason": "assistant-request-returned-no-assistant",
            "inboundPhoneCallDebuggingArtifacts": {
                "error": "Couldn't Get Assistant. Either Set The Assistant I D On The Phone Number. Or, To Debug Your Assistant Request, Check The Debugging Artifacts That Were Just Sent To Your Server.",
                "assistantRequestError": "Couldn't Get Assistant. Assistant Request Did Not Return One.",
                "assistantRequestResponse": "{ \n\"assistantId\": \"f177bcaf-d97d-4c81-acb4-bfb836818474\",\n \"assistant\": {\n\"name\": \"Form Submission
This is the response that went to the server
s
You just need to provide one thing
assistantID or assistant parameter.
s
I have the assistantId in the module
The module that calls the webhook to create an assistant in Make
Copy code
{ 
"assistantId": "f177bcaf-d97d-4c81-acb4-bfb836818474",
 "assistant": {
"name": "Form Submission",
"voice":
s
remove the whole parameter of "assistant"
s
like this?:
Copy code
{ 
"assistantId": "f177bcaf-d97d-4c81-acb4-bfb836818474"{
"name": "Form Submission",
"voice":
I'm replacing it with "assistantOverrides" to see if it works
Nothing worked
I tried with and without assistant override
Fixed it I had a "created at" in the json and I believe that's what' prevented the assistant from coming up
s
Awesome.
4 Views