I am using VAPI for voice agent, makes cold calls. I have my own CRM built using reactjs. All of sudden, my conversation is not being automatically passing to my CRM but when triggered manually.

It sounds like you're experiencing an issue where conversations from your VAPI voice agent are no longer being automatically sent to your ReactJS CRM, even though manual triggering still works. While I don't have specific troubleshooting steps available, I understand how disruptive this can be. If you have any more details about recent changes or error messages, feel free to share them, and I'll do my best to help.

Check that your Vapi webhook is still correctly configured and active, and verify your CRM endpoint hasn’t changed or encountered errors, as the issue likely lies in webhook delivery.

Actually my webhook shows 200 ok in vapi UI , but not reflect in CRM, then in webhook response field also shows "no conversation" after the call end, i use webhook for trigger 2,3 things, the other webhook logic works perfect , but the fetching data logic only not works.

Ensure your webhook response follows the correct JSON format with the proper toolCallId, responds promptly to avoid timeouts, and is properly integrated with your CRM via an API request node in your Vapi workflow. Use debugging tools to check for errors or warnings..

I think i done all your points, but still i face the same issue from past 2 days , in webhook response filed not shown a conversation details , i modified the code in backend as much as possible , but my issue is not solved.

It sounds like you've been thorough in checking your webhook setup and backend code, especially since other webhook logic is working and you're seeing a 200 OK status. Since the issue is isolated to fetching conversation data and the webhook response field shows "no conversation" after the call ends, it might help to double-check if there have been any recent changes in how conversation data is generated or made available by VAPI. Sometimes, even small updates or changes in data structure can affect what gets passed through the webhook. Reviewing any recent updates or logs around the time the issue started could provide more clues. You're clearly putting in a lot of effort to resolve this, and I hope you're able to pinpoint the cause soon!

Hey, Could you please schedule a brief call at your convenience so we can discuss this matter in detail? Kindly use the following link to book a suitable time: .