Connector Improvement: Ability to spin up duplicate connectors with different endpoint parameters
AnsweredFor the Trisolute data connector (specifically the "serp_visibility_chart" table), we will likely need to create duplicate versions of that same table, with slightly different query parameters.
We are hoping to use this connector to replace a job that hits the following endpoint:
https://app.newsdashboard.com/
However, we anticipate the need to set up duplicate versions of this same job using different values of apiFilter. So we may have one job running that hits
https://app.newsdashboard.com/
and down the road, want to add another job that hits
https://app.newsdashboard.com/
We don't yet know what the necessary values of apiFilter will be. These will likely shift with evolving stakeholder demands.
We would like a way to spin up new instances of this connector using to-be-determined values of apiFilter and were hoping this is something you could help with. Thanks!
-
Official comment
Hi Jason,
Thank you for reaching out and sharing your feature request regarding the Trisolute data connector and the need to create duplicate versions of the "serp_visibility_chart" table with different query parameters. We genuinely appreciate your input and the detailed context you’ve provided.
I'm pleased to confirm that we have added your request to our backlog. As with all feature requests, it will be prioritized based on overall demand and alignment with our product strategy. Please rest assured that we will keep you updated on any progress or developments regarding this feature.
Thank you once again for your valuable feedback and for being an engaged member of our community. If you have any further questions or additional insights to share, please don't hesitate to reach out.
Best regards,
Syead Mujtaba Imam Rizwi
Please sign in to leave a comment.
Comments
1 comment