It would help to explain what kind of integration you're expecting; because while Ktor and Exposed can complement each other well in the same project, they're separate tools and I don't see much need for them to really know about each other.
In 'clean architecture' terms, Ktor's routing abilities may be thought of as your backend's presentation later, while Exposed works great at implementing a repository/service layer for your data. If you're expecting a kind of turn-key CRUD functionality for any named Entity, neither framework is yet that opinionated about how it should be achieved, AFAIK you would have to fill that gap in for yourself.
Actually that's something I really like about Ktor, other well known JVM web frameworks seem like an impenetrable nightmare to me because they are so heavily opinionated that you will face many obstacles unless you understand the original designers philosophy, which only comes after a lot of time.