Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Decoupling Connectors from Destinations to Improve Reusability and Efficiency

Planned
Andrey Parahnevich User

Current State:
Each new connector is configured as a one-to-one relationship with a specific destination. This means that for every new destination, a separate connector setup is required.

Proposed Improvement:
Decouple connectors from destinations to enable a more flexible, reusable architecture. A single connector should support multiple destinations, allowing users to simply select an available destination from a dropdown rather than creating a new connector instance.

Goal:
Increase efficiency, reduce configuration overhead, and promote reusability by separating connector and destination configurations.

Thank you
Andrey Parahnevich  

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Amy Peterson Fivetranner

    Hi Andrey,

    Thanks for the feedback! We do have this capability on our medium-term roadmap, as it's a fairly common ask.

    I am interested in learning more about your use case—specifically, what workflows or challenges prompted this request, and how you envision managing connector-to-destination assignments within your organization.

    Thanks,
    Amy