I have a scenario made to connect vapi ai with make to check availability. The webhook response is set up well with the required json format like
{
“results”: [
{
“toolCallId”: “X”,
“result”: “Y”
}
]
}
After the scenario runs, make is fetching the right answer but vapi is giving a different answer that is seperate from what make is giving. Hopefully i can get an assist soon enough
1 Like
Hi@Jeremiah_Adeyemo,
It seems like the issue lies in ensuring the correct result is passed back to VAPI AI. Please double-check that the result fetched by Make is correctly mapped
If the issue persists, you can try adding a small prompt or clarification in VAPI AI to guide it toward providing the desired response. For example, include a hint in the system prompt or output format that aligns with the expected result structure.
This is an example :
Feel free to share more details if you need further assistance!
Best regards,
Msquare Automation
Platinum Partner of Make
@Msquare_Automation
1 Like
hey, I have the same problem, I did return a header that specifies the content-type : application/json from make but the agent stills not recognize the result, I see in the message that ```
No result returned for <call_Id>
1 Like
@johnDoe1
Hi, we’re here to help.
Could you please send me a screenshot of the webhook response output?
1 Like
Hi there! Did you managed this?
I’m facing the same situation: Vapi with wrong response and Make with correct one.
Hi @JulesAI, @Jeremiah_Adeyemo
This problem usually occurs when the JSON structure of the webhook response breaks. The issue is likely due to line breaks in your response Y.
If Y contains a list, make sure it’s separated by commas instead of line breaks or bullet points. If Y consists of paragraphs, use \n to maintain proper JSON formatting. This should ensure that the JSON remains intact and prevents VAPI from interpreting a different response than Make.