Hi! I have an issue with the “end of call” function: the webhook created on Make.com is not triggered when the assistant works through twilio if I do a test directly on Vapi instead then it is triggered. Can anyone help me?

Hi there! I understand you're having an issue with the "end of call" webhook not triggering in Make.com when your assistant works through Twilio, but it works fine when tested directly on Vapi. To help troubleshoot this issue, could you please share more details about: 1. How exactly have you configured the webhook in Make.com and how is it referenced in your Vapi assistant? 2. Are you using any specific method to end the call in your assistant (like the

say

method with

endCallAfterSpoken=true

or the

end-call

message type)? 3. Do you see any error messages in either the Vapi logs or Make.com scenario execution logs? 4. Have you verified that the webhook URL in your Vapi configuration exactly matches the one provided by Make.com (no typos or extra spaces)? This information will help me pinpoint the specific issue in your Twilio-Vapi-Make.com integration! 🕵️‍♂️ Sources: - [End of call function in Vapi](https://docs.vapi.ai/changelog/2025/1/14) - [Troubleshooting webhooks in Make.com](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336345690393149452) - [Vapi-Twilio integration](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336407849806462976) - [Webhook configuration with Make.com](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362)

Hey! To help track down this issue, could you share: - The call ID - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!