Bug Report – Webhook URL Not Saving
# support
v
Hi there! 👋 I understand you're having trouble saving your Webhook URL in VAPI. Unfortunately, I can't see the specific error message you're receiving. However, I can definitely help with this issue as this appears to be a known bug in the VAPI platform. According to the information I found, there are several known bugs related to saving Webhook URLs, Server URL Secrets, and Headers in VAPI: ## Known Issues Several users have reported similar problems where settings are not saved or are unset shortly after being saved. According to reports, users often receive a "Success: Your changes have been saved" message, but the note at the top still says "You have unsaved changes" - exactly what you're experiencing. One user reported: "I have the same issue today. I restarted my ngrock server so I had to change the url. The url says it's updated but I'm not getting any message callbacks. When I try adding headers, it doesn't get saved." This matches your situation closely. ## Potential Causes The issue could be related to: - A bug in the VAPI UI (which has been acknowledged by the VAPI team) - Server URL secret being removed automatically - Headers not being saved correctly - Issues with editing the secret (which can erase it) ## Troubleshooting Steps Here are some steps you can try: 1. Refresh the page after putting in the key, which might help save it 2. Clear your browser cache and cookies, or try using a different browser 3. Inspect network activity using your browser's developer tools to look for failed requests 4. Double-check the URL for any typos or accidental spaces 5. Check server logs to see if there are any errors affecting the webhook calls ## Workarounds Since this appears to be a known bug that will be fixed in a future release, here are some workarounds:
1. Use the API instead of the UI - A VAPI team member has suggested using the API for adding server secrets and headers as a temporary workaround until the dashboard v2 is released 2. Delete and recreate - Some users have resolved similar issues by deleting the old assistant and creating a new one 3. Re-add the secret - If you're experiencing issues with adding headers, re-adding the secret might work (but be careful not to edit it afterward, as that can erase it) Would you like me to provide more specific information about any of these troubleshooting steps or workarounds? Sources: - [Bug: Webhook URL, Server URL Secret, and Headers Not Saving](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1331991829717188680) - [Workaround: Use the API to save headers and secrets](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334552736133546076) - [Bug: Server URL Secret Not Persisting](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341692740454584331) - [Bug: Editing the secret erases it](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - [Troubleshooting steps for Webhook URL not saving in VAPI](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336399188665040968)
s
We got the same issues. My changes in my assistant are not saving instantly. Have to do it over and over again before it saved. Been 3 days, and its not yet resolved )):
f
The problem is that you don't allow you to put a URL in HTTP, you only allow you to save HTTPS
I would like to have confirmation from you and know if we can still use http?
89bb2a68-8187-4cc8-ab57-217814ed6eb2
Would it be possible to have an answer?
s
Hey, friends yours, apologies for the delay. It's true that you can only make use of HTTPS, not HTTP. It's obvious because of security protocols.
You have also shared some UUID, I would like to know what do you help require related to this ID?
f
Hello, Here are the details of the issue I'm encountering: • Organization ID: 89bb2a68-8187-4cc8-ab57-217814ed6eb2 I had configured several bilingual agents (FR–EN) which were working perfectly. I then proceeded to add webhook information in the organization settings to receive data from VAPI into N8N. After completing this setup, I tested one of the agents to make sure everything was working properly. Unfortunately, I noticed that none of the agents can hear or function anymore after responding to the first question from the AI. Additional details: • No other changes were made except for the webhook configuration. • I saw a prompt saying I could update the agents, which was suggested by VAPI, and I followed through with it. • Since performing that update, nothing is working anymore. Could you please help me identify and resolve the issue? It is urgent that my agents are able to function again. Thank you very much for your support. Best regards,
k
We are looking into it
s
@François Okay, as you've mentioned that none of your assistants can hear or respond after the first message. If you could share the call ID (any of the recent call IDs), then I can debug and investigate
f
I had to deal with the problems on my own, you can close the tickets