The Conduit team and our community of developers are always adding new connectors. Don't see the connector you need below? Help us prioritize by creating new issues, commenting, or leaving a
+1 on our source
and destination connector lists.
Don't have time to wait? You can get started building your own in no time.
Built-in vs Standalone
A Conduit connector can run in one of two ways built-in or standalone. Built-in refers to connectors that are compiled into the Conduit binary, while standalone refers to connectors that run separately from Conduit. You can learn more about standalone vs built-in connectors on our Connector Behavior page. A small set of connectors are built into Conduit by default. For those connectors no additional setup is required and you can start using them in Conduit right away.
Conduit- These are connectors that are built by the Conduit team. Any issues or problems filed on those repos will be responded to by the Conduit team.
Community- A community connector is one where a developer created a connector and they're the ones supporting it, not the Conduit team.
Legacy- Some connectors are built using non-preferred methods. For example, Kafka Connect connectors can be used on Conduit. This is considered a stop-gap measure until
communityconnectors are built.
At this time, Conduit does not have any commercially supported connectors.
Source means the connector has the ability to get data from an upstream data store. Destination means the connector can write to a downstream data store.
|Azure Cosmos DB||WIP||WIP||Community|
|Google Cloud Storage||✅||Community|
|Kafka Connect Wrapper||✅||✅||Legacy|