Can plain-language workflow descriptions actually become production-ready without significant rework?

I’ve been reading about AI copilots that supposedly let you describe a workflow in English and have it automatically generate something deployable. That sounds too good to be true, and I’m skeptical about whether the output actually works or if it’s just generating 50% of what you need and leaving you with more work to finish.

We’re evaluating moving some of our Camunda workflows to see if we can reduce the development burden. The appeal of just writing out what we want in plain language is obvious—less time spent in visual builders or writing code. But I need to understand what typically breaks. Does the AI understand conditional logic? Can it handle error cases? What about integration complexity—if I describe a workflow involving three different APIs, does it wire them up correctly or does that require manual adjustment?

I’m not asking if it’s perfect; I’m asking if it’s actually useful for real workflows or if it’s just a nice demo. Has anyone actually used a copilot to generate workflows that went into production with minimal tweaking?