Hey all, I am sending a webhook response from make.com and depending on the response, my agent is meant to either verify the user or not but it disregards the response and always verifies the user. Any ideas on how to solve this would be much appreciated. Thanks

cc: @Kings_big💫

It sounds like your agent is not correctly interpreting the webhook response from make.com and is always verifying the user, regardless of the response content. Since Vapi is designed to let you manage workflows and business logic, you might want to double-check how your agent is parsing and acting on the webhook response. Make sure that the logic handling the webhook response is correctly checking the relevant fields or status codes before deciding whether to verify the user. If possible, try logging the actual webhook response your agent receives to ensure it's in the expected format and that your conditional checks are working as intended. If you can share more details about your current setup or the webhook response structure, I might be able to offer more targeted suggestions.

Ensure your webhook response from Make.com correctly includes and matches the toolCallId, with a clear verification result that your Vapi assistant checks to decide whether to verify the user or not..

Thanks for sharing your issue! Could you please provide a sample of the webhook response from Make.com and indicate which field your agent should use to determine if the user should be verified? This will help in giving you a more precise solution.

thanks for you response. and @Shubham Bajaj Thanks for bringing this to "Kings_big" attention. The issue was that I set "async" to "true". I have changed this to "false", but now my agent just stays silent. When checking the webhook logs. I get a 200 response with the message and relevant toolCallId, so not sure what the issue is. Thanks

To help diagnose why your agent stays silent after setting

"async": false

, could you please share the exact JSON payload of the webhook response you are sending from Make.com (with sensitive data redacted)? This will help verify if the structure and fields (especially

toolCallId

and the verification result) match what Vapi expects and allow for more targeted troubleshooting. Sources: - [Vapi Custom Tools Guide](https://docs.vapi.ai/tools/custom-tools) - [Vapi Tool Calling Integration](https://docs.vapi.ai/customization/tool-calling-integration)

Your webhook response format matches Vapi's requirements, but the agent may not be able to interpret the

result

field for verification unless it receives a specific value or structure. Could you clarify what value or format your agent expects in the

result

field to determine if the user should be verified? This will help ensure your webhook response is structured correctly for your use case. For reference, see the [Vapi Custom Tools Guide](https://docs.vapi.ai/tools/custom-tools). Source: - [Vapi Custom Tools Guide](https://docs.vapi.ai/tools/custom-tools)

Hi all, this is solved. I changed "async" to false and "strict" to true

Great job resolving the issue! Setting "async": false ensures your agent waits for the webhook response, and "strict": true makes the agent only proceed if the response is valid and matches the expected structure. This is the recommended approach for reliable verification flows with Vapi custom tools. For reference, see the [Vapi Custom Tools Guide](https://docs.vapi.ai/tools/custom-tools). Source: - [Vapi Custom Tools Guide](https://docs.vapi.ai/tools/custom-tools)

Make sure your webhook response includes the exact toolCallId, a plain string result, proper JSON formatting, Content-Type: application/json, and that your assistant’s tool configuration is correct..

That's excellent advice! Ensuring your webhook response includes the correct

toolCallId

, a clear result, proper JSON formatting, and the right Content-Type helps maintain smooth communication between your assistant and Make.com. Keeping your tool configuration aligned with these best practices will support reliable verification flows.

checking if this is resolved/solved for you?

It looks like you previously confirmed the issue was solved after updating your settings. If anything else comes up or you have more questions, feel free to let us know!

It was array of things. Not having "Content-Type: application/json", setting "async" to "true" , having "strict" set to "false" and adding messages. Thanks

Thanks for sharing the details of what resolved your issue! It's great to hear that updating the "Content-Type" header, setting "async" to false, and "strict" to true did the trick. Your summary will definitely help others facing similar challenges.

Working fine now

That's great to hear! If anything else comes up in the future, feel free to reach out.