Custom Connector Source Only in No Code Interface

Slack Knowledge Base Q&A Connector Development
, , , ,
1

Summary

User building a custom connector via the no code interface needs it as a destination instead of just a source. Is this a bug or a feature?


Question

i’m building a custom connector via the no code interface and i see it’s only available as a source, but i need it as a destination. is this a bug or a feature ?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["custom-connector", "no-code-interface", "source", "destination", "bug", "feature"]
2

got it whats my alternative

3

There are a several destinations in our repository, you could build one using the Python CDK.

destination-pinecone could be an example. But, that’d be more involved.

4

Neither. The connector builder only works to build sources. It isn’t in the roadmap for now to make possible to run with/as destinations.