Display same config fields in Connector card as are available in Fivetran dashboard connector creation
AnsweredFeature request
Add the same fields present in the Fivetran Dashboard connector creation flow to the Connector Card. Some inputs are left out in the Connector card rendering it impossible to setup a connector the exact same way through the REST API + Connector card as would be possible through the Fivetran Dashboard
Problem we encountered
We rely on the Connector card for our users to create connectors within different Fivetran warehouses. There are some connectors that require additional fields according to the REST API Fivetran exposes. For example Google Analytics has a required field for "tables" and "metrics" are also supposed to be provided. Once such connector is created the Connector card doesn't display the dropdowns that the Fivetran dashboard connector flow has. The below image highlights the fields I am talking about. It would be amazing if these fields for this (and other) connector(s) would also be present on the Connector card.
Why request this feature?
As briefly alluded to above, we rely on having our users create connectors through Connector cards. Our users will never get to the Fivetran dashboard so all of the connector management needs to be done through API calls as well as the Connector card. A solution that we could build ourselves is that we allow the user to fill out this missing information before actually creation the connector, this only has some downsides:
- We don't have access to the source, rendering it impossible for us to help users out with suggesting the contents of the required fields
- We would need to practically copy the exact same thing that you've done, including documentation
- This approach makes our end very error prone once things change within connectors on your end
If anything remains unclear about the feature requested/problem encountered/motivation behind the feature request I am more than willing to elaborate!
-
Official comment
Hi Floris, thats so much for this feature request! We built Connect Card for a very specific use case - a customer who wants to onboard data from their end users but own the data experience / consistency of the data that pulls through. It sounds like you're trying to build something that is not consistent across all users but enables user customization. I'd love to learn more about what you're building and how we can help. I'll email you separately to set up some time.
Please sign in to leave a comment.
Comments
1 comment