I’ve configured a Server URL in Vapi to send events to my n8n webhook/workflow. This had been working, but for the past few days no assistant-request messages are being sent to the webhook anymore. What could be causing this? Could it be related to Twilio? I purchased a second Twilio number for my voice agent because call forwarding didn’t work on the previous number; with the new number, forwarding works. Thanks for your help.

Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team

Suggestion: Check that your new Twilio number in Vapi has the correct Server URL configured to point to your n8n webhook. Server URLs can be set at the phone number, assistant, or organization level, but the phone number setting takes priority. To verify or update: 1. Go to the Vapi dashboard → Phone Numbers. 2. Select your new Twilio number and ensure the Server URL field is set to your n8n webhook endpoint. If the Server URL is missing or incorrect, assistant-request webhooks will not be sent to your workflow. [See more on Server URL priority and configuration](https://docs.vapi.ai/server-url/setting-server-urls) Source: - [Setting server URLs](https://docs.vapi.ai/server-url/setting-server-urls)

Server URL is set

I solved a similar for someone just now, If you wouldn't i could also help you the issue.

Would be awesome

Have you tried checking the geo-permission section to see if your location number is permitted..

@GIDEON the webhook still receives events like "end-of-call-report" and "status-update" just not "assistant-request" anymore.

Good to know you did, how then were you able to find a better solution.

@Fabio @GIDEON I had similar issues, here's what I was missing: 1. webhook server url to be configured for phone number : in addition to the assistant, you need to configure the phone number to point to the webhook to get the asssistant at the beginning of the call. the assistant-request is before the assistant is spawned, so that config needs to go in the preceding actor, which is the number 2. use the api to configure the phone number: currently the phone number config on dashboard doesn't let you configure a number with no assistant and a server url. After this, I was able to use assistant overrides to configure assistant ta the start of the call.

The dashboard will actually allow you to configure a phone number without assistant, squad, and workflow associated. If an assistant is selected, just open the dropdown and select it again to disable it. Its a little unintuitive, but it works.

Thank you