Not reaching make.com
# support
z
Hi! I have a tool that for some reason it's not reaching make.com, if I try to run it on postman, works well, but not in the tool. I can't figure out what's happening Call id cd2bd22e-f213-4154-ad80-0dc35c6b0325
a
HeyZe Thank you for creating the ticket! A member of our team will reach out to you shortly.
v
You can continue this conversation by mentioning me in the message.
@Ze Hello! I'm here to help you troubleshoot the issue with your tool not reaching make.com. Since it works well on Postman, it's likely that the issue is related to the configuration or network settings within the tool itself or the environment where it's running. To assist you better, could you please provide me with more details about the tool you're using and the specific error messages or behaviors you're observing when you attempt to connect to make.com? Additionally, it would be helpful to know if there are any differences in the headers, body, or method between the Postman request and the one from your tool.
z
I dont see any difference
v
@Ze Understood. If there are no visible differences in the request details between Postman and your tool, we may need to look into other potential issues such as: 1. Network configurations: Ensure that the network settings allow outbound connections to make.com. 2. Authentication: Verify that any required authentication tokens or credentials are correctly set up in your tool. 3. Headers: Double-check that all necessary headers are included and correctly formatted. 4. Endpoint URL: Confirm that the endpoint URL is correct and accessible from the tool's environment. 5. Proxy settings: If your tool is behind a proxy, ensure that it's configured properly. Since the issue seems to be specific to the tool's environment or configuration, I would recommend checking the above points. If you're still unable to resolve the issue, please provide any error logs or messages you receive when attempting the connection, as they can offer more clues to the underlying problem. If you need further assistance, don't hesitate to ask.
z
ask for humam support
v
@Ze Please ask support for more info on this.
z
Just found what was happening, I was specifing a data structure, and it was not matching
s
logs
first-tool-call-repsonse
šŸ”µ 10:50:47:601 Server Message Successful. (https://hook.eu2.make.com/s8g3u). Response: { "results": [ { "toolCallId": "call_choKmdslU31UJDabum0UVYIT", "result": [ { "event_type": "https://api.calendly.com/event_types/aa", "scheduling_url": "https://calendly.com/j", "description": "Google meet call - not in person", "type": "virtual", "location": "virtual" }, { "event_type": "https://api.calendly.com/event_types/", "scheduling_url": "https://calendly.com", "description": "Google meet call - in person", "type": "local", "location": "Istanbul, Turkey", "start_date": "2025-02-18", "end_date": "2025-02-21" } ] } ] }
second-tool-call-response
šŸ”µ 10:51:09:739 Server Message Failed. (https://hook.eu2.make.com/63tfi49ah2lra). Error: šŸ”µ 10:51:09:740 [user ERROR] tool-calls Server URL Error: Request failed with status code 400
@Ze As you can see in the logs first tool call failed because of response format is incorrect and for the second one your server failed to respond.
@Ze Checkout this documentation on how to do tools calling effectively https://docs.vapi.ai/tools-calling#server-response-format-providing-results-and-context
@Ze because of no response closing this ticket.
2 Views