Question on workflows. I'm wondering if the programatic method of creatign workflows via the API is supported robustly? If we eng up creating thousands of workflows via the API, is this somethign Vapi has intentionally designed for? Or was the intention to have customers create O(dozens) of workflows mostly through the web UI? Appreciate any advice from members or Vapi team?

Yes, Vapi is designed to robustly support programmatic creation of thousands of workflows via its API, it’s API-first and built for scale, so the web UI is optional, and most limitations will come from your own backend or cost management not Vapi itself..