Every integration platform I have ever used eventually told a customer no. Not because the work was impossible, but because the system they needed was not in the connector catalog, and adding it meant waiting on a roadmap. The catalog model guarantees that the one system unique to your business is the one you cannot reach.
This release put the Connector Copilot into beta, and it is our answer to that whole problem.
Connect by describing it
With the Connector Copilot, you create a dataset from a REST API using natural language. No custom code, no waiting for us to build a connector for your specific system. You point it at the API, describe what you need, and you get a live connection to a system that was never on anyone’s list.
The same release expanded plain-language support across the board, so that every transformation, not just a subset, is reachable through the conversational interface. The goal is consistency: the way you connect a source is the same way you shape its data, in plain language, with review.
Why this changes the question
The catalog model makes “can it connect to X” a question about our backlog. This makes it a question about whether X has an API. Usually it does.
For the engineering behind how the copilot reads a system and stands up a connection, my co-founder wrote it up in how it was built. For the founder version, it is simpler than that. We decided long ago that we did not want to build a catalog. We wanted to build something that could connect to systems we had never seen. This beta is the clearest step toward that yet.
More on the platform on the platform page.