I am using make to do outbound calls with vapi through an http request, there's a part in my system prompt where it uses a function that i assigned to my agent in vapi to check calendar for available dates, but the function is not working when i do it through the http request. How do i make sure the fucntion call is done https://cdn.discordapp.com/attachments/1359254033386443145/1359254033902338370/Screenshot_2025-04-08_154820.png?ex=67f6cf77&is=67f57df7&hm=b2ee4d78b5883011ab1f8c8dbb442212384d78e9e8192e37982d3854f7e3f347&

Hi there! 👋 I see you're having trouble with a Vapi function call not working when triggered through an HTTP request from Make.com. While I can't see the specific details of your system prompt or function implementation, I can definitely help with ensuring your function calls are executed correctly. Here are several steps to ensure your Vapi function call is properly executed: ### 1. Check Your HTTP Request Structure Make sure your HTTP request to Vapi is properly structured. According to [Vapi documentation](https://docs.vapi.ai/server-url/events), the request body should follow this format:

json
{
  "message": {
    "type": "function-call",
    "call": { Call Object },
    ...other message properties
  }
}

### 2. Verify Function Requirements For a function to be called properly in Vapi, you need: - The correct function name and endpoint - All necessary parameters (like attendee name, date, time) - Proper headers and authentication tokens - The appropriate HTTP method (usually POST for webhooks) As mentioned in a [Discord thread](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336345690393149452), these elements are essential for successful function execution. ### 3. Troubleshooting Steps If your function still isn't working, try these troubleshooting steps: - **Check Logs**: Look at both Vapi and Make.com logs for errors or warnings - **Verify Webhook URL**: Ensure there are no typos in your webhook URL - **Test Manually**: Try triggering the Make.com webhook manually using Postman or cURL - **Check Authentication**: Verify that your API keys and authentication details are correct - **Review Payload Format**: Ensure the data format sent from Make to Vapi matches what's expected ### 4. Alternative Approach

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!

I got it right thanks

Marking this ticket as Solved ✅