Within make.com I'm getting this error when running the caller: Error: 400 Bad Request {"message":"Couldn't Get Tool.

toolId

509ae25b-306d-486a-9541-1d24acb9c5c4 Does Not Exist.","error":"Bad Request","statusCode":400} The strange thing is that the tool IDs do exist with VAPI and even successfully sent test data to make.com. I've attached the Json code that I'm using as well as confirming that my tools do in fact exist. What can I do to fix this? https://cdn.discordapp.com/attachments/1357768452169011281/1357768453410394185/image.png?ex=67f167e9&is=67f01669&hm=9944f80fcd9bbc0f0165888fb20d2a48406167c36a1716d34c7a71a6bc21a1e7& https://cdn.discordapp.com/attachments/1357768452169011281/1357768453825757184/image.png?ex=67f167e9&is=67f01669&hm=de7759acd6242c72ef092f26d5d4288ce222c16003af5a42ad76013af8c7b62b& https://cdn.discordapp.com/attachments/1357768452169011281/1357768454710759605/image.png?ex=67f167e9&is=67f01669&hm=4be8021d5c238c013708e3c40d70fabe8521d22466a69770e735f2f0948e1a16&

Hi there! 👋 I see you're running into that frustrating "Tool ID Does Not Exist" error when integrating VAPI with make.com. I can't provide specific information about your "Dare2Activate" setup, but I can definitely help troubleshoot why you're getting this error despite the tool IDs existing in VAPI. Based on the information I found, here are several potential causes and solutions for this issue: ### 1. Check JSON Response Format The most common cause is an incorrect JSON response format. Make sure your response follows this exact structure:

json
{
  "results": [
    {
      "toolCallId": "<your-tool-call-id>",
      "result": "Your result as a string without line breaks"
    }
  ]
}

Line breaks in your JSON response can cause this error, as [tool calls expect results without line breaks](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342176467714572400). ### 2. Verify Tool Configuration Ensure the

toolId

property is not present in the

tools

array in your configuration. According to [troubleshooting documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333880245681393756), this can cause the exact error you're seeing. ### 3. Check API Authentication Verify your API key setup is correct: - Check the VAPI Dashboard under the Provider Keys tab to ensure your API key is added and validated - In make.com, ensure you're including the Authorization header with the 'Bearer' schema followed by your API key - If you see "No Private Key Found," you might need a private key in addition to your API key ### 4. Webhook Configuration Double-check that: - The webhook URL in VAPI exactly matches the one provided by make.com - The data structure being sent from VAPI matches make.com's expected format - Required headers or authentication tokens are included correctly ### 5. Try Recreating the Tool

any updates @User ? Thanks

Thank you for reaching out to us. We've received your message and will get back to you as soon as possible.

No it has not been resolved @User

Please have some patience Shubham Bajaj will be with you soon thanks

Hey Jose, your using wrong API key your tool is registered under orgId

8821c67f-1ccb-4971-8c5a-8e08de8f1379

but your using orgId

1148f68f-c8b1-48f0-bb31-31fc794c9de6

😅 thank you, this fixed the issue

Marking this ticket as Solved ✅