trying to set up a tool that sends details to Make.com. matched the URL, confirmed the tool’s name and parameters, verified scenario is active on Make.com, but no data shows up in the endpoint or Vapi logs indicating the tool call was triggered. anyone else run into this or have tips on getting the tool to actually fire?

Heycbulm84 Thank you for creating the ticket! A member of our team will reach out to you shortly.

@cbulm84 It sounds like you've done a thorough job setting up your tool to send details to Make.com. Here are a few tips that might help you troubleshoot the issue: 1. **Double-check the URL and Tool Name**: Ensure that the URL you've configured in VAPI exactly matches the webhook URL provided by Make.com. Also, confirm that the tool's name in VAPI matches the one expected by Make.com. 2. **Review HTTP Method**: Make sure that the HTTP method (GET, POST, etc.) you're using to call the tool matches the method expected by the Make.com scenario. 3. **Check API Key/Authentication**: If Make.com requires an API key or any form of authentication, verify that it's correctly included in your tool configuration. 4. **Inspect Request Payload**: Ensure that the payload you're sending with the tool call has the correct format and contains all the necessary parameters expected by Make.com. 5. **Examine Make.com Scenario Logs**: Look into the scenario execution logs on Make.com to see if there are any errors or indications that the scenario was triggered but failed to process the data. 6. **Test with a Simple Tool Call**: Try setting up a simple tool call with minimal parameters to see if that works. This can help isolate whether the issue is with the data being sent or the connection itself. 7. **Network Issues**: Check if there are any network issues or firewalls that might be blocking the HTTP request from reaching Make.com. 8. **Contact Support**: If you've tried all the above and still can't get the tool to fire, it might be helpful to reach out to VAPI or Make.com support for further assistance. If you need any specific actions to be taken from the VAPI side, please let me know, and I can assist you further.

confirmed the webhook URL, tool name, HTTP method, and authentication settings. also tested with minimal parameters, checked the Make.com scenario logs, and don’t see any sign of the call.

Hey @cbulm84 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 me figure out what went wrong!