Assistant Request Not Triggering
# support
c
@Shubham Bajaj not sure why this is happening but I keep getting a "status-update" instead of assistant request when calling a number which has a webhook attached. never seen this before. Me and @Jack McKague are both having the error in real time. Did something change recently?
v
@Chowderr I'm sorry to hear that you're experiencing issues with the webhook functionality. There haven't been any recent changes that should cause such behavior. It's possible that there might be a misconfiguration in the webhook settings or a temporary glitch in the system. To assist you better, could you please provide me with more details about the webhook configuration and the exact steps you're taking when you encounter this issue? This will help me understand the problem and guide you towards a resolution. If the issue persists, I would recommend reaching out to support for a more in-depth investigation.
You can continue this conversation by mentioning me in the message.
j
Yeah so for some reason now, it's working on @Chowderr 's side but not on mine. He is now getting the type as "assistant-request" in make, while I am still getting the type as "status-update" in make and n8n
c
Even before that i was not even getting the assistant request. I was only getting status-update for some time. The only thing I changed was caller from a Google Voice number.
@Shubham Bajaj
4fb3cedb-55c9-45a9-ba15-9aec0fbec7cb 74b75f05-927b-4116-b4cd-65a3f1cbfd5b 6c60ea66-d091-4a06-af67-68403e040615 6d188447-93b8-4851-8dcf-fac5b59ef6c7 feee1283-d4cb-44af-882c-1ae6de8a9ff0
Just bought some new numbers and still getting a status update.
s
@Chowderr can you share the phoneNumberId?
c
Of the previous calliDs?
s
The phone number ID for which you have added the server URL and want to receive assistant-request server events not call id.
c
43f94ebe-7a34-4150-9875-a465c5d6ab5f
s
logs
🔴 19:04:53:353 PATCH /phone-number/43f94ebe-7a34-4150-9875-a465c5d6ab5f, BadRequestException 400 (NoCodePrenuers, 2a06:98c0:3600::103) Response: { "message": "PhoneNumber Not Found", "error": "Bad Request", "statusCode": 400 } Request: { "headers": { }, "body": { "server": { "url": "https://n8n.otakusolutions.io/webhook/6a8bfc47-84b4-4429-9468-f9ad39681ca5" } }, } 🔴 18:51:14:793 PATCH /phone-number/43f94ebe-7a34-4150-9875-a465c5d6ab5f, BadRequestException 400 (Otaku Solutions, 2a06:98c0:3600::103) Response: { "message": [ "server.url must be a valid URL. Hot tip, the protocol should be https:// or wss://, but found \"" ], "error": "Bad Request", "statusCode": 400 } Request: { "headers": { }, "body": {"server": {"url": "\""}}, "url": " }
@Chowderr As you can see from the logs, first your server URL was not assigned because it was empty, and then the number was deleted. I suggest using the API client or referencing the documentation to update your phone number. You can find the server URL documentation here: https://docs.vapi.ai/api-reference/phone-numbers/update
Do let me know if you face any difficulties or have any doubts.
c
I only use the API. Before I delted the Twillio number and added it back all I did was add a server URL and started getting the error.
Besides that I just bought a brand new number and it's still the same error
@Jack McKague please put some calliD's you did.
@Shubham Bajaj
s
@Chowderr Can you share the new phone number ID and server URL you want to add? I will help set it up and then we can do the test call.
c
This is the new iD 2fa91ee2-434f-4e11-b4e7-ca7c8979cc89 https://n8n.otakusolutions.io/webhook/6a8bfc47-84b4-4429-9468-f9ad39681ca5
s
@Chowderr Try now I have updated the server url for your phone number.
c
Could you share the curl as well?
Also when i call nothing hits my server.
s
I updated from the DB.
c
s
@Chowderr could you share your response payload along with a Loom video?
j
I’ll put some call Id’s shortly
And retest
Any luck @Shubham Bajaj
s
@Jack McKague @Chowderr Nothing wrong on our side. You're sending the response payload a little here and there. Could you share your response payload along with a Loom video?
j
Yeah do I just include the loom video in this thread @Shubham Bajaj
?
c
And callID @Jack McKague
s
a gentle reminder @Jack McKague .
c
@Shubham Bajaj was the docs updated for phone numbers. For some reason now I get "property provider should not exist" ?
s
No your doing something definitely wrong.
c
Just used Postman to update and i still get the same error. CalliD: 7ca06719-1beb-43c6-84d7-0ae7167270df
e1d0f03f-81c4-4d5a-8fa3-1efcc41c60d3
s
@Chowderr use the following curl request. I'm not sure why this issue is only occurring for you since it's working for everyone else. You'll need to replace your phoneNumberId, ApiKey, and ServerUrl, and then it should work. Do let me know your thoughts on this.
request
curl -X PATCH https://api.vapi.ai/phone-number/insert-phone-number-here \ -H "Authorization: Bearer insert-token-here" \ -H "Content-Type: application/json" \ -d '{ "provider": "vapi", "server": { "url": "insert-your-server-url-here" } }'
c
If itsnot to much can you do a Twillio one for me. I will d testing and update
s
@Chowderr You can copy and paste this into Postman and it will work. Otherwise, you will need to share the key, phone number ID, and server URL.
c
You mean SID and Auth token?
s
No your Vapi Private Key, Phone Number Id and Server Url. Give it a try, you will be able to do it.
c
Some confusion. I also need a request for Twillio numbers as well.
s
just set the provider to twilio.
Only this works for me: { "server": { "url": "https://n8n.otakusolutions.io/webhook-test/c17c8147-34bc-4516-8d24-84298d39a83a" } }
s
@Chowderr share the phone number id and server url I will get it done.
c
@User So when I put a serverURL on my Org level I get an "assistant-request" but when i set on phone number level I still get errors. e37e641b-9bb9-41c6-9ab7-b5f4a8e0144b "1729e412-f9fd-499c-b987-16bc154dede9",
s
can you set once on phoneNumber
server.url
and then let me know the phone-number-id, I will do deep investigation to see.
These phone-number-id's doesn't exists.
c
I just deleted them last night. Will do momentarily.