@BeanSquid I'm sorry to hear you're having trouble connecting VAPI to Make.com. It sounds like there might be an issue with the configuration of your VAPI assistant or the way it's integrated with Make.com. The request for a passcode could be a security measure set up within your VAPI configuration. To assist you better, I'll need a bit more information: 1. Have you set up any security features such as a passcode within your VAPI settings? 2. Can you confirm if the server URL and the serverUrlSecret are correctly configured in your VAPI settings? 3. Have you checked the logs on Make.com for any errors or messages that might indicate what the issue is? Once we have more details, we can troubleshoot the issue further. If you have any specific error messages or configurations you can share, that would be very helpful.

your scenario doesn't make sense. you have a trigger which is basically just a scheduled trigger and you also have a webhook. A webhook receives responses. you shouldn't have both.

Bryce for reference it is only showing one of the webhooks in the history note in the screenshot not the other webhook i dont know why that is (but there was two webhooks and a HTTP at one point. I juggled these around a bit trying to make it ork until i got past the "could not get assistant" robo voice to answer question 1 and 2 - NO i had the url secret on then took it off (tried doing this three times) that did not work. I set up a authorization code with my API key in make .com that also did not work.

@BeanSquid It seems like you're encountering an issue where Make.com is unable to fetch the assistant from VAPI. This could be due to a few different reasons, such as incorrect configuration settings, network issues, or an issue with the VAPI service itself. To troubleshoot this issue, please consider the following steps: 1. Double-check the assistant ID to ensure it's correct and corresponds to the assistant you're trying to use. 2. Verify that the API key and any other authentication credentials are entered correctly in Make.com. 3. Ensure that there are no IP restrictions or firewall settings that might be blocking the request from Make.com to VAPI. 4. Review any error logs or messages on both Make.com and VAPI for clues as to why the connection is failing. If you've already tried these steps and the issue persists, it might be necessary to reach out to the support teams of both Make.com and VAPI for further assistance. They may be able to provide more detailed insights based on their system logs and configurations. If you provide me with any specific error messages or codes you're receiving, I can offer more targeted advice. Otherwise, if you feel this issue is beyond your control, please ask support for more info on this.