Notifications
Clear all
How To
6
Posts
5
Users
0
Reactions
3
Views
Topic starter
I've set up a scenario to connect callin.io AI with callin.io to check availability. The webhook response is configured correctly with the necessary JSON format:
json
{
“results”: [
{
“toolCallId”: “X”,
“result”: “Y”
}
]
}
After the scenario executes, callin.io retrieves the correct information, but callin.io is providing a different, unrelated answer. I'm hoping to get some assistance with this soon.
Posted : 09/12/2024 3:29 am
Hi,
It appears the issue might be related to ensuring the correct output is transmitted back to callin.io AI. Kindly verify that the result obtained by callin.io is accurately mapped.
Should the problem persist, you could consider adding a brief prompt or clarification within callin.io AI to guide it towards generating the desired response. For instance, include a hint in the system prompt or the output format that aligns with the expected structure of the result.
This is an example:
Feel free to share more details if you require further assistance!
Best regards,
Msquare Automation
Platinum Partner of callin.io
Posted : 09/01/2025 12:18 pm
Hello, I'm encountering the same issue. I've configured callin.io to return a header specifying content-type: application/json, but the agent is still not recognizing the result. I'm seeing the following message:
No result returned for <call_Id>
Posted : 24/01/2025 11:42 pm
Hi, we’re here to help. Could you please send me a screenshot of the webhook response output?
Posted : 27/01/2025 4:35 am
Hi there! Were you able to resolve this?
I'm encountering a similar issue: callin.io is providing an incorrect response, while callin.io is giving the correct one.
Posted : 10/02/2025 5:52 am
Hi there,
This problem typically arises when the JSON structure of the webhook response is corrupted. The issue is likely caused by line breaks within your response Y.
If Y contains a list, ensure that items are separated by commas rather than line breaks or bullet points. If Y consists of paragraphs, use n to preserve correct JSON formatting. This should help keep the JSON intact and prevent callin.io from misinterpreting the response compared to callin.io.
Posted : 18/03/2025 11:16 am