i have connected VAPI call assistant with shopify, so whenever someone orders on my shopify store, VAPI calls the customer. i have setted up VAPI using HTTP "make a request" module. now i want it to update a google sheet with the call ended reason. but i cannot get the call ended reason in the HTTP output, i need it to update my google sheet according to the call end reason. i am sharing the json code. pls check if someone can help https://cdn.discordapp.com/attachments/1317165116357214281/1317165116659073075/Json_Code.txt?ex=675db11b&is=675c5f9b&hm=1475ab517b2692954eb02d02a53664fe3e84a9af545707f61fab616c2b4ddb9e&

@LP Gaming Certainly! To help you better, I'll need to see the JSON code you're referring to. Please share the JSON output you're getting from the HTTP "make a request" module, and I'll guide you on how to extract the call ended reason from it. Once we have the call ended reason, we can discuss how to update your Google Sheet accordingly.

Got it. Tagging @User for additional help.

@Vapi it is not capturing the endcall report

@LP Gaming I understand that you're having trouble capturing the end-of-call report in your HTTP module output. The end-of-call report should be sent as a POST request to the Server URL you've specified in your VAPI call assistant setup when a call ends. Here's what you need to ensure: 1. **Webhook Configuration**: Make sure that your VAPI call assistant is configured to send a POST request to a webhook URL that you control. This webhook should be set up to receive the end-of-call report. 2. **Server URL**: Verify that the Server URL in your VAPI setup is correct and that the server is capable of receiving POST requests. 3. **Request Handling**: Your server should have an endpoint that is set up to parse the JSON body of the incoming POST request. The JSON body will look like this:

json
{
  "message": {
    "type": "end-of-call-report",
    "endedReason": "hangup"
  }
}

4. **Google Sheets API**: To update a Google Sheet, you'll need to use the Google Sheets API. You'll have to write a script or use an integration platform that can take the

endedReason

from the JSON and update the Google Sheet. 5. **Testing**: Test the entire flow to ensure that the end-of-call report is being captured and that the Google Sheet is being updated accordingly. If you're not receiving the end-of-call report, you may need to check the logs on your server or the service that's supposed to capture the webhook to see if there are any errors. If you're still having trouble, please provide more details about your current setup, including how you've configured the webhook in VAPI and the method you're using to attempt to capture the end-of-call report. If there's a specific error message or behavior you're encountering, that information would also be helpful.

@Vapi the status is showing queued pls help

@LP Gaming If the status of your VAPI call is showing as "queued," this typically means that the call has been accepted by the system but has not yet been initiated or is waiting for available resources to proceed. Here are a few steps you can take to troubleshoot this issue: 1. **Check Call Volume**: If you're making a large number of calls simultaneously, you might be hitting some concurrency limits. Ensure that your call volume is within the limits of your VAPI plan. 2. **Review Configuration**: Double-check your VAPI configuration to ensure that there are no errors in the setup that might be causing calls to remain in the queue. 3. **Network and Carrier Issues**: Sometimes calls can be queued due to network congestion or carrier issues. This is often temporary and may resolve on its own. 4. **Webhook for Status Updates**: Make sure you have a

statusCallback

URL configured to receive asynchronous updates about the call status. This URL should point to a server that can handle POST requests and update your systems accordingly. 5. **Server Capacity**: Ensure that the server handling the webhooks has enough capacity to process incoming requests and is not causing a bottleneck. 6. **Logs and Monitoring**: Check the logs for your VAPI service and your webhook server to see if there are any errors or warnings that could explain why calls are stuck in the queue. 7. **Contact Support**: If you've gone through these steps and the issue persists, it may be best to contact VAPI support for further assistance. If you need to update your configuration to include a

statusCallback

URL or make any other changes, please provide the necessary details, and I can guide you through that process.