Connector Improvement: Annotations / Labels for Connectors and Destinations
AnsweredAs Fivetran usage scales across teams, environments, and data domains, managing connectors and destinations becomes increasingly difficult. Today, there is no native way to attach structured metadata to Fivetran resources (connectors, destinations), which makes organization, ownership tracking, cost attribution, and automation more cumbersome.
Many infrastructure and cloud platforms (e.g., Kubernetes, AWS, GCP) solve this with labels/annotations or tags that allow users to logically group, filter, and manage resources without relying on naming conventions alone.
Proposed Feature
Introduce support for user-defined annotations / labels / tags on Fivetran resources such as:
- Connectors
- Destinations
These labels would be simple key–value pairs, for example:
team=analytics
owner=data-platform
environment=prod
cost_center=finops
data_domain=marketing
Expected Capabilities
-
Add, edit, and remove labels via: Fivetran UI, REST API
-
Filter and search resources in the UI by label
-
Retrieve labels via API for automation and reporting
-
Use labels for programmatic governance and lifecycle management
-
Official comment
Hi Yegor,
Thanks for this feedback. We've heard similar suggestions from other customers and it is something we are exploring. To help ensure we address your needs, could you share more about your specific use case? What challenges are you currently facing due to the lack of resource tags within Fivetran?
Updates regarding our progress will be shared here with the community.
Thanks,
Amy -
Hi Yegor,
Thank you for your detailed feedback and request! We are assessing this feature request to understand scope, solutions and alignment with our roadmap.
We will share an update on this thread regarding our evaluation as soon as its available.
Thanks,Naren - Fivetran Team
-
+1 Strongly support this enhancement.
As organizations scale their Fivetran footprint across multiple teams, environments, and data domains, relying solely on naming conventions becomes increasingly difficult to manage and govern.
Native support for labels/tags on connectors and destinations would significantly improve:
- Ownership and accountability by clearly identifying business and technical owners
- Cost allocation and showback/chargeback through attributes such as cost center, business unit, or project
- Environment management (dev, test, prod) and operational visibility
- Automation and governance by enabling API-driven reporting, policy enforcement, and lifecycle management
- Searchability and organization of large numbers of connectors and destinations
This capability is already considered a best practice across many cloud and infrastructure platforms, and bringing similar functionality to Fivetran would greatly improve enterprise-scale administration and FinOps reporting.
We would find tags such as
team,owner,environment,cost_center, anddata_domainparticularly valuable for governance, auditability, and internal chargeback/showback processes. -
This feature is has my overwhelming support.
Please sign in to leave a comment.
Comments
4 comments