VAPI•7mo ago

End of call Custom Fields not working with make.com

Everyone that uses make.com with VAPI now have issues with the end of call report.

Because if you work with the transient assistant JSON Code it automatically transforms {{endedReason}} {{rubric}} {{schema}} {{transcript}} in make.com fields as you can see in the screenshot. Thats why its not working anymore.

Anyone has a solution?

Bildschirmfoto_2025-06-23_um_10.35.09.png

KyleAPP•6/23/25, 8:44 AM

Hi fabi,

Check and update your Make.com scenarios to ensure they correctly handle these placeholders based on how Vapi transmits them post-update. If transformations occur unexpectedly, you might need to adjust the JSON or mapping rules within Make.com to accurately capture and interpret these fields.

Please review your current configurations in Make.com and verify they align with the latest Vapi updates regarding field handling.

awake-maroonOP•6/23/25, 12:56 PM

Yeah but how to update the make szenarios. Because Make.com uses the same mapping rules as VAPI. Thats why I can not send {{endedReason}} in the make.com http module.

KyleAPP•6/24/25, 11:04 PM

We are actively looking into this issue and will reach back out to you once we have an update. I will also loop in my colleague to get his perspective from this as well @shubham

End of call Custom Fields not working with make.com

Similar Threads

Similar Threads

Similar Threads