ivana 9:19 am
Hi everyone. I have noticed that I am not receiving a “call_analyzed” webhook anymore if the disconnection reason is “dial_no_answer” and simmilar. Can someone confirm that logic has changed so that I can update my n8n workflow?
Based on the available documentation, when a call has a disconnection reason of dial_no_answer, the call status is not_connected, meaning the outbound call did not connect because the number dialed did not answer(1).
According to the webhook specification, when a call did not connect (such as calls with dial_failed, dial_no_answer, dial_busy disconnection reasons), the call_started webhook will not be triggered(2). However, both call_ended and call_analyzed webhooks should still be triggered(2).
The documentation also notes that post-call analysis fields will not be populated for calls that were not connected or where no conversation took place(3). You should check whether the call_analysis field exists before using it(3).
If you’re not receiving call_analyzed webhooks for dial_no_answer calls, this may be related to the fact that no analysis is being performed since no conversation occurred. I recommend checking your webhook logs and verifying that your endpoint is properly configured to handle all webhook event types.
For additional support with this issue, you can:
- Ask questions on Discord
- Visit Contact Sales
- Visit https://github.com/RetellAI/
Thank you for your answer. If the workflow was not changed by your side then it is a bug. I have not received a “call_analyzed” webhook for multiple calls in a past few days. Can someone please check this?
Hello @ivana, if the call doesn’t start, no webhook will be triggered.