Hi, can someone provide me with our websocket url? I really want this to move on with my development. Thanks in advance!

@Bosstechnerd Absolutely, I'd be happy to help with that! However, the specific websocket URL you need would typically be provided by your organization or the service you're using for your development. If you're referring to a websocket URL for VAPI, it would be the server URL that you expose to VAPI to receive conversation data in real-time. If you have already set up a server URL for your VAPI application, you would use that as your websocket endpoint. If you haven't set one up yet or are unsure about the details, please refer to our server URL guide for instructions on how to create and use one. If you need the guide or further assistance with setting up your server URL, please let me know!

Please assist because I don't know which step to take from here.

@Bosstechnerd I understand that finding the correct websocket URL can be a bit tricky. Since you're using Make.com, you'll typically need to set up a scenario where you integrate VAPI with Make.com's modules. Here's a general step-by-step guide to help you: 1. Create a Webhook in Make.com: - Log in to your Make.com account. - Create a new scenario. - Search for the 'Webhooks' module and select it. - Choose 'Custom webhook' and create a new webhook. - Make.com will provide you with a unique URL to send data to. 2. Configure Your VAPI Application: - Use the URL provided by Make.com as the server URL in your VAPI application settings. - This URL will be the endpoint VAPI sends conversation data to, which Make.com will listen for in real-time. 3. Test the Connection: - Send a test request from your VAPI application to the Make.com webhook URL to ensure that the connection is working correctly. If you're still having trouble or if any of these steps are unclear, please let me know, and I can provide more detailed assistance or direct you to support for further help.

How do I send a test request from VAPI application

@Bosstechnerd To send a test request from your VAPI application to the Make.com webhook URL, you would typically follow these steps: 1. Prepare the Test Data: - Determine the type of data your VAPI application will send. This could be a JSON object with fields that your webhook is expecting. 2. Use a REST Client or Command-Line Tool: - You can use tools like Postman or command-line tools like

curl

to send a test request. 3. Send the Test Request: - Set the request method to

POST

(or another method if specified by your webhook configuration). - Include the necessary headers, such as

Content-Type: application/json

. - Set the request body to the JSON object you prepared. - Use the Make.com webhook URL as the request URL. Here's an example using `curl`:

bash
curl -X POST -H "Content-Type: application/json" -d '{"test": "data"}' YOUR_MAKE_WEBHOOK_URL

Replace

YOUR_MAKE_WEBHOOK_URL

with the actual URL provided by Make.com and

{"test": "data"}

with the actual test data you want to send. If you need assistance with crafting the test data or using a specific tool to send the request, please let me know, and I can provide further guidance.

So I added the Server Url in my VAPI Server URL Organisation Settings. When I call the agent it does not receive data. When does it fire?

@Bosstechnerd The server URL you set in your VAPI organization settings should receive data whenever a call is made to your VAPI application. Here are a few things to check to ensure that it fires correctly: 1. **Correct Server URL**: Verify that the server URL you've entered in the VAPI settings is correct and exactly matches the one provided by Make.com. 2. **Endpoint Configuration**: Ensure that the endpoint on your server is configured to accept POST requests and that it is set up to receive JSON payloads if that's what VAPI is sending. 3. **Webhook Activation**: Make sure that the webhook in Make.com is activated and ready to receive data. 4. **Network Issues**: Check if there are any network issues or firewalls that might be blocking incoming requests to your server URL. 5. **VAPI Configuration**: Confirm that your VAPI application is correctly configured to send data to the server URL for the events you are interested in. 6. **Logs and Errors**: Look at the logs on both the VAPI side and the Make.com side to see if there are any errors or messages that could give you a clue as to what's going wrong. 7. **Test Environment**: If you're testing in a development or staging environment, make sure that the server URL is not limited to a production environment. If you've checked all of these and the data is still not being received when you call the agent, it might be best to reach out to VAPI support for a more in-depth investigation. They can help you troubleshoot the issue by looking at the specifics of your account and configuration.

@Bosstechnerd you can use webhook.site to get a webhook for your testing.