My make.com scenario sends a webhook response telling the assistant that a booking was successful, but this is never received by the bot, in the logs it says: { "name": "NewAvailabilityTool", "role": "tool_call_result", "time": 1722537584138, "result": "No result returned.", "toolCallId": "call_5WyrLFSULLpXPJx0YDENOB26", "secondsFromStart": 25.399 } showing that the result is not sent. I dont know if maybe the webhook takes too long to send the result or something but I know the bot isn't saying the right follow up statements as if the meeting is booked. 3a8abd50-a8c9-4659-938e-295b142fe2a3 is the call ID The Webhook setup is attatched. { "role": "tool_calls", "time": 1722537580496, "message": "", "toolCalls": [ { "id": "call_5WyrLFSULLpXPJx0YDENOB26", "type": "function", "function": { "name": "NewAvailabilityTool", "arguments": "{\"TimeRequested\": \"next Monday at 4 PM\"}" } } ], "secondsFromStart": 21.757 } Above is the tool call message from the call. Thanks! https://cdn.discordapp.com/attachments/1268641308939911283/1268641309275717703/image.png?ex=66ad29ca&is=66abd84a&hm=6143047c475b226be89832578900f84b259e4f9fb6fa331c8d44f5ee392bb34e& https://cdn.discordapp.com/attachments/1268641308939911283/1268641309757935770/image.png?ex=66ad29ca&is=66abd84a&hm=451182694f81238acb7e55eea90aa32c8c85679018ef8ffd982beb300643508b&

@NathanO It seems like there might be an issue with the webhook configuration or the response time. Webhooks typically need to respond within a certain time frame to ensure the calling service receives the expected data. If the response from your make.com scenario is taking too long, the bot might not receive the result in time, leading to the "No result returned" message you're seeing in the logs. To address this, you can check the following: 1. **Webhook Response Time**: Ensure that the make.com scenario is optimized to send the response as quickly as possible. Any delays in processing within the scenario could cause a timeout. 2. **Webhook Configuration**: Verify that the webhook URL and payload are correctly configured in make.com. The payload should match the expected format that the bot can understand. 3. **Network Issues**: Sometimes, network latency or issues can cause delays in webhook responses. Check if there are any such problems that could be affecting the response time. 4. **Error Handling**: Implement error handling in the make.com scenario to ensure that any issues during the booking process are caught and a proper response is sent back to the bot. 5. **Logs and Testing**: Review the detailed logs from make.com and test the scenario to ensure it's triggering correctly and sending the expected response. If you've checked all the above and the issue persists, it might be beneficial to reach out to make.com support for further assistance with the scenario configuration. Additionally, if there's a possibility to adjust the timeout settings on the bot's side, that could also be explored. If you need further assistance with the bot or webhook configuration, please ask support for more info on this.

Everything seems right to me I dont know why it isnt responding, the response its giving is just [ Null ]

I was sure that had to be in JSON

I solved the issue I think by making sure the make,com webhook response body was in the following JSON format: { "results": [ { "toolCallId": "REPLACE TOOL CALL WEBHOOK ID HERE", "result": "REPLACE THIS WITH WHATEVER YOU WANT SENT BACK TO VAPI" } ] } Hopefully anyone with the same issue can find this now and it will be resolved quicker because to me it doesnt make sense for the body to have to be JSON when it is just a string that needs to be sent back to the Vapi assistant.

A string is just one response though right? So it kind of makes sense. Glad you got it though.