Stream Clipper
12/14/2025, 3:50 PMAI Evy
12/14/2025, 3:50 PMAI Evy
12/14/2025, 3:50 PMAI Evy
12/14/2025, 3:50 PMcall_analysis.custom_analysis_data object. [(1) ]()
The response structure shows:
json
"call_analysis": {
"call_summary": "...",
"in_voicemail": false,
"user_sentiment": "Positive",
"call_successful": true,
"custom_analysis_data": {}
}
So for your custom field caller_full_name, the path in Make.com would be:
call_analysis.custom_analysis_data.caller_full_name
A community member who encountered a similar issue with Make.com found success by following a specific workflow for properly capturing the call_analyzed webhook event. [(2) ]() The key insight shared was that the call_analyzed webhook is only sent after the call ends (not during ongoing calls) , so ensure you're testing with a completed call.
If the variables still don't appear in Make.com's mapping panel after a webhook determination, you may need to manually send a sample call_analyzed request using a tool like Postman to properly define the data structure in Make.com.AI Evy
12/14/2025, 3:50 PM