Asistant is not calling Custom Tool
# support
m
Hi, I set my first custom Tool (webhook using n8n), and when i try to make the first call (to capture the toolCallId) i see calls from agent never arrives, on vapi logs, i see he says is a 404 error calling the url (but dont see which url is trying to, so i can't debug it), in any case. I triple check, and set custom tool again, and my webhook url is correctly setted, working, and online. Anyone can help me with this? Thanks in advance
v
message has been deleted
@Marcos Ramírez Hello! I'm sorry to hear you're experiencing issues with your webhook setup. To assist you better, I'll need to gather a bit more information. Could you please confirm if you have set the server URL on your account or on the specific assistant that you're trying to use with your custom tool? Additionally, ensuring that the URL is accessible from the public internet and not just locally is important for VAPI to reach it. If everything seems correct on your end, there might be an issue with how the URL is being called from VAPI. To help you debug this, I can check the server URL settings for your account or specific assistant. Could you please provide me with the relevant details so I can look into this for you?
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
m
I just need to ensure is trying to call the correct url
What details you need?
@Vapi what relevant details you need? im just trying the assistant uses the tool: https://flows.marcosramirez.dev/webhook/14367f98-f993-456f-9eb6-dac956a532ae and he says is a 404, when is not
v
@Marcos Ramírez Thank you for providing the webhook URL. It seems like there might be a discrepancy between the URL you've set and what VAPI is attempting to call. To ensure that VAPI is using the correct URL, I would recommend the following steps: 1. Double-check the webhook URL in your VAPI settings to ensure there are no typos or errors. 2. Verify that the webhook URL is publicly accessible and not blocked by any firewalls or security settings. 3. If possible, check the logs on your webhook server to see if there are any incoming requests from VAPI. If after these steps the issue persists, please provide the following details so I can assist you further: - The exact name or identifier of the custom tool you've set up in VAPI. - Confirmation that the webhook URL is publicly accessible and has been tested independently of VAPI (e.g., via a tool like Postman or cURL). With this information, I can help you troubleshoot the issue more effectively. If you have already verified these details and the problem continues, please let me know so we can explore further solutions.
m
@Vapi I triple check the url, and is correct
v
@Marcos Ramírez I understand that you've confirmed the webhook URL is correct and publicly accessible. Since you're still encountering a 404 error when VAPI attempts to call your webhook, we may need to investigate this further internally. To proceed, could you please provide the following information: 1. The name or identifier of the custom tool you've configured in VAPI. 2. The exact time and timezone when you attempted to make the call and encountered the 404 error. 3. Any additional configuration details you provided when setting up the custom tool in VAPI. With this information, I can look into the logs and configuration on our end to determine why VAPI is not able to successfully call your webhook. If you have any other relevant details or observations, please share them as well. If you're unable to provide this information here or if you prefer to handle this through a more secure channel, please reach out to our support team directly with the details, and they will be able to assist you further.
m
@Vapi where can i directly reach the support team?
v
@Marcos Ramírez Please ask support for more info on this.
m
Silly failure, VAPI allways makes POST calls (and i was expecting a GET.. just in case any other is having the same problem)
Stills not working... post call don't get my server