@Built over 600 agents that makes sense in your case it’s less about can it connect and more about how cleanly VAPI can sit as the orchestration layer between Qualiflow and your custom CRM. VAPI can definitely play that role, especially for handling call logic, state, and routing, while Qualiflow handles its native flows. The main thing is designing the event flow properly so you don’t get latency or broken state between systems. On my side, I’ve built a few agent setups around Qualiflow-style workflows and external orchestration (including VAPI), mostly where we had to bridge into custom CRMs or third-party tools. So I’m quite familiar with the edge cases you’ll likely run into. If you want, I can take a quick look at your architecture and suggest the cleanest way to structure it