Here is the JSON payload which I am using in HTTP module

{ "assistantId": "{{32.assistant_id}}", "assistantOverrides": { "variableValues": {{33.json}} }, "customer": { "number": "{{30.phone}}", "name": "{{30.first_name}}" }, "phoneNumberId": "{{32.phone_number_id}}" }

Here is the result of HTTP request https://cdn.discordapp.com/attachments/1314074775697621053/1314075339860742196/image.png?ex=67527387&is=67512207&hm=22d01887efb1eef60d8dae5cda367b3098571480a21e25b30d9fc7fd9dc24988&

@Ch Adeel Hello! I'm sorry to hear you're experiencing issues with outbound calls through Make.com. It sounds like the calls are being initiated but not reaching the customer as expected. Let's troubleshoot this together. Since the calls work correctly when initiated from the VAPI dashboard, it suggests that the issue might be with the integration between Make.com and VAPI. Here are a few things to check: 1. **Webhook Configuration**: Ensure that the webhook used to trigger the HTTP module in Make.com is correctly configured with the right URL and method (POST/GET). 2. **HTTP Module Settings**: Double-check the HTTP module settings in your Make.com scenario. Verify that the headers, body, and other parameters match exactly what's required by VAPI. 3. **Authentication**: Confirm that the authentication token used in Make.com is valid and has the necessary permissions to make outbound calls. 4. **Customer Number Format**: Make sure the customer number is in the correct international format and that there are no formatting issues when passing it through Make.com. 5. **Timing**: Investigate if there's a delay between the trigger and the actual HTTP request. Sometimes network delays can cause unexpected behavior. 6. **Voicemail Detection**: The VAPI might be detecting voicemail too quickly. Check if there are settings related to voicemail detection that you can adjust. 7. **Logs and Error Messages**: Review the logs in both Make.com and VAPI for any error messages or warnings that could provide more insight into the issue. If after checking these points the issue persists, it might be necessary to look deeper into the integration or even reach out to Make.com support for further assistance. If you have any specific error messages or logs that you can share, that would also help in diagnosing the problem.

You can continue this conversation by mentioning me in the message.

Got it. Tagging @User for additional help.

And here is the second call ID which I made using the inbuild outbound calling module inside Vapi dashboard the number is same for both calls caa93c13-598e-4a48-ac95-a0169df84fc1

I have tried it multiple times and also I am building the same system for another project but same issue is happening there

@Shubham Bajaj can you look at this please?

Hello @Shubham Bajaj can you please help with this?

And this is happening in both of my outbound projects

I've two different projects for two different clients but I'm facing the same issue in both projects

@Shubham Bajaj Can you help please it's an urgent project I've to deliver it today but it is not working