[400] Bad Request Origin Vapi Automatic error handler If you want to handle this error automatically, choose one of the following options. This will create a new error-handler route in your scenario. You can then expand the route in any way you like. Can't seem to find the error. Need somewhere to start troubleshooting. Using Google sheets to batch call numbers with make.com Added the make.com script manually with the webhook url, changed the sheet to sheet1 and range to A1:a1000 added the phone number ID and assitant ID from Vapi Both Make and Vapi had an update so some of the settings are different from the video I watched to integrate the tools. Is there something I'm missing?

Hi there! 400 Bad Request errors can be frustrating 😓 Based on the information you've provided, here are some troubleshooting steps to help resolve your issue: ### Common Causes of 400 Bad Request Errors 1. **Incorrect JSON Format**: Make sure your data is properly formatted when being sent through the webhook [source](https://discord.com/channels/1211482211119796234/1211483291191083018/1325000684231196775) 2. **Missing Required Fields**: Recent updates might require specific fields like

provider

in your requests [source](https://discord.com/channels/1211482211119796234/1211483291191083018/1340615317772308520) 3. **Headers Configuration**: Ensure your

Content-Type

header is set to

application/json

[source](https://discord.com/channels/1211482211119796234/1211483291191083018/1330221332452999321) ### Troubleshooting Steps 🔍 1. **Verify Webhook URL**: Double-check that your webhook URL is correctly entered and functional [source](https://discord.com/channels/1211482211119796234/1211483291191083018/1335141023600480318) 2. **Check HTTP Method**: Confirm you're using the correct HTTP method (POST, GET, etc.) [source](https://discord.com/channels/1211482211119796234/1211483291191083018/1335141023600480318) 3. **Review Make.com Logs**: Check the scenario logs in make.com for specific error details [source](https://discord.com/channels/1211482211119796234/1211483291191083018/1335141023600480318) 4. **Test with Postman**: Try testing your webhook endpoint with a tool like Postman to verify connectivity [source](https://discord.com/channels/1211482211119796234/1211483291191083018/1336345690393149452) 5. **Verify Authentication**: Ensure your API keys and authentication credentials are correct [source](https://discord.com/channels/1211482211119796234/1211483291191083018/1335141023600480318)

Based on your description and my research, I see several potential issues that could be causing the 400 Bad Request error: 1. Incorrect API endpoint formatting: In Make.com, when making an API call to Vapi, you need to make sure you're using the relative URL path rather than the absolute URL. Several community posts show this is a common error. 2. Wrong request body format: The structure of the JSON you're sending to Vapi's API may not be formatted correctly. 3. Authorization/authentication issues: Your Vapi API credentials may not be correctly configured in Make.com. 4. Google Sheets range formatting: The range specification for your Google Sheets data might be causing issues. 5. Missing or incorrect parameters: Required parameters like phone number ID or assistant ID might be incorrectly specified. ## Troubleshooting Steps Here's how I recommend troubleshooting this issue: 1. Check the Webhook URL format in Make.com: - Make sure you're using the relative URL path rather than the absolute URL - For example, use /call instead of https://api.vapi.ai/call 2. Verify your request body format: - The body structure for Vapi outbound calls should include: - The phone number ID - The assistant ID - The customer phone number (from Google Sheets) 3. Check your Google Sheets configuration: - Confirm that your sheet name is exactly "Sheet1" (case-sensitive) - Verify that your range "A1:A1000" is correctly formatted - Ensure the phone numbers in your Google Sheet are properly formatted (with country code) 4. Verify your Make.com modules: - Ensure you have the correct modules connected in the right order - Typically, the flow should be: Google Sheets → HTTP/API Request to Vapi 5. Review the Vapi logs: - Check the Vapi dashboard for more detailed error logs about the 400 Bad Request ## Specific Recommendations From what I've seen in the Make.com community discussions, the most common issue with Vapi integrations and 400 Bad Request errors is incorrect request formatting. Try the following: 1. In your Make.com HTTP/API module that's calling Vapi: - Use /call as the relative URL path - Set the method to POST - Ensure your headers include:

Content-Type: application/json

     Authorization: Bearer YOUR_VAPI_API_KEY

- Format your body like this:

json

     {

       "phoneNumberId": "YOUR_PHONE_NUMBER_ID",

       "assistantId": "YOUR_ASSISTANT_ID",

       "customer": {

         "number": "{{formatPhoneNumber}}"

       }

     }

Where formatPhoneNumber is a variable from your Google Sheets that contains the phone number to call 2. Make sure your phone numbers in Google Sheets are in E.164 format (e.g., +15551234567) 3. If you're still getting errors, try making a simple test call with hardcoded values first to verify your Vapi API connection is working correctly. Let me know if you try these steps and if they help resolve your issue.