So here is my prompt: Even after using a tool/function and running a webhook on make.com the webhook gets triggered at the end of each call but the data as well as the number and name of person called does not come through. https://cdn.discordapp.com/attachments/1267847083516362874/1267847083986260122/image.png?ex=66aa461c&is=66a8f49c&hm=541bbb6aeb58a4568b5da26caf1e0d88336eb7001712c3eb4717ff28f2c003ff& https://cdn.discordapp.com/attachments/1267847083516362874/1267847084355223552/image.png?ex=66aa461c&is=66a8f49c&hm=0c966b5c567a65713b4edd47b5a74fcc8e75f58a8d33d0b59bd477856ca3828e& https://cdn.discordapp.com/attachments/1267847083516362874/1267847084686708809/image.png?ex=66aa461c&is=66a8f49c&hm=0bed4b013c67afde7724500dc799cadf22f01b08098ee65f6cbf618ef2189c8d& https://cdn.discordapp.com/attachments/1267847083516362874/1267847085059997849/image.png?ex=66aa461c&is=66a8f49c&hm=9844592e7a37ecd897d1c282f8e7c70036f6f5420eb8db4ac62d6be94908fdfd&

@Araiz It sounds like you're experiencing an issue with your webhook integration on make.com, where the webhook is being triggered but not receiving the expected data. To assist you better, I would need a bit more information: 1. Can you confirm if the webhook is configured correctly to receive the data you're expecting (number and name of the person called)? 2. Have you checked the logs on make.com to see if there are any errors or messages that could provide more insight into the issue? 3. Is there any specific format or structure that the data should be sent in from the source system to the webhook? Once you provide this information, I can give you more targeted advice on how to resolve the issue. If you're unsure about any of these details, please ask support for more info on this.

@User As for as my knowledge the webhook is configured correctly, but what is the ideal configuration? Yup I'm getting a bunch of replies within the logs Example: [ERROR] status-update Server URL Error: Request failed with status code 410 [ERROR] end-of-call-report Server URL Error: Request failed with status code 410

@Araiz The status code 410 indicates that the resource available at the target URL is no longer available, which is why the server is returning an error. This could mean that the endpoint you've set up for the webhook on make.com is pointing to a URL that was valid but has since been removed or is no longer accepting requests. Here's what you can do to resolve this issue: 1. Verify the Endpoint URL: Ensure that the URL you have provided for the webhook in make.com is correct and that the server at that URL is operational. 2. Check for Endpoint Changes: If the endpoint URL has changed or the server has been reconfigured, update the webhook settings with the new URL. 3. Server Availability: Make sure that the server is running and is configured to accept POST requests at the endpoint URL. 4. Contact the Server Administrator: If you do not have control over the server, contact the administrator to find out why the resource is no longer available. 5. Update Webhook Configuration: If the endpoint has been intentionally removed, you will need to set up a new endpoint and update the webhook configuration to point to the new URL. If you've checked all of these and the issue persists, it might be best to reach out to make.com support for further assistance, as they can provide more detailed guidance based on their system's specifics.

@Vapi the webhook gets triggered but still no data comes through

@Araiz If the webhook is being triggered but no data is coming through, there are a few potential issues that could be causing this problem: 1. **Payload Configuration**: Ensure that the payload you expect to be sent to the webhook is correctly configured. The data fields (like the number and name of the person called) should be properly mapped and included in the payload. 2. **Content-Type Header**: Check if the

Content-Type

header is set correctly in the request. For JSON data, it should be

application/json

. 3. **Data Parsing**: Verify that the server handling the webhook is correctly parsing the incoming requests. If the server expects JSON, ensure that it's parsing the JSON body correctly. 4. **Webhook Settings**: Double-check the webhook settings in make.com to ensure that it's set to send the data you're expecting. Sometimes, you may need to explicitly specify which data to send. 5. **Error Handling**: Implement error handling on the server to log any issues when trying to parse or process the incoming data. This can help identify if the data is arriving in an unexpected format or if there are parsing errors. 6. **Testing Tools**: Use tools like Postman or cURL to manually send test payloads to your webhook URL to ensure that the server is handling the requests correctly. 7. **Firewall or Security Settings**: Make sure that there are no firewall or security settings that are blocking the incoming data or stripping it out. 8. **Check Documentation**: Review the documentation for the service that is sending the data to the webhook to ensure that you are following their guidelines for receiving data. If you've gone through these steps and the issue is still not resolved, it may be helpful to reach out to make.com support or the support for the service that is sending the data to the webhook for further assistance. They may be able to provide more specific guidance or identify if there is an issue on their end.

@Vapi still not solved

@Araiz I'm sorry to hear that the issue persists. Since the problem is quite specific and might require a detailed look into your webhook configuration and the system you're integrating with, I recommend reaching out to make.com's support team for a more in-depth investigation. They will be able to guide you through the process of diagnosing the issue with your webhook and can provide assistance tailored to their platform. Additionally, if the problem lies with the service sending the data, you may need to contact their support team as well. Please ensure you have all relevant information on hand when you contact support, such as: - The exact configuration of your webhook on make.com. - Any error messages or logs that you have. - The expected data format and payload. - Any tests you have performed, such as sending manual requests to the webhook URL. If you need further assistance or have other questions, feel free to ask.

can you please share the call id.

@Shubham Bajaj Heres the id: 23970046-131d-466b-b8bb-7cc88d980ff5 So the agent will call through an airtable sheet and on the call it will ask if the lead is looking to sell their property if so then store property type, location and reason for selling. This is the data i need.

@Araiz Please ask support for more info on this.

@Vapi is it since i've not paid up yet?

@Araiz As a support bot, I don't have access to your payment information or account status. However, it's important to ensure that your account is in good standing and that all necessary payments have been made, as some services may restrict access to certain features or support if there is an outstanding balance. If you suspect that the issue with the webhook not transmitting data might be related to payment status, I recommend checking your account details with the service provider or reaching out to their billing department to confirm that everything is up-to-date. They will be able to provide you with information regarding your account and whether any payment issues could be affecting your service.

You are not showing a picture of your webhook or anything. You sure you are not just mapping the data?

@Araiz your assistant is missing server url please add it and then you will get the end of call report.

@Shubham Bajaj server url can be a webhook too right?

yes it can be a webhook url where vapi will send end of call report

However when i create a function i have added a url in that. Whats the difference between both?

one is for your tool call and another for assistant related api requests

so both those URL's can be the same?

just add server url to the assistant and you will get the end of call report.

@Shubham Bajaj sir it still does not work

dm me.

sent

Can i do call records ? @Vapi

@. Yes, you can enable call recording in VAPI. However, please remember that if

hipaaEnabled

is set to true, no logs, recordings, or transcriptions will be stored to ensure compliance with HIPAA regulations. If

hipaaEnabled

is false and

recordingEnabled

is set to true, then calls will be recorded by default. Always ensure that you have the necessary permissions and are compliant with all relevant laws and regulations when recording calls. If you need to change the recording settings or have any specific questions about implementing call recording, please let me know, and I'll assist you further.