New Connector: Slack Enterprise Grid Data Collector
At HackerOne, like many enterprise companies, we use Slack Enterprise Grid. A every specific product that creates an umbrella account around several, dozens, or hundreds of workspace. HackerOne, while a small company (450 employees) has over 3000 guest users and 2600 slack connect members. Slack does not make tracking this data back to CRM's, Internal tools, Support portals, etc easy. We would love to bring this data into Snowflake via Fivetran to better understand our users. Who are they, what account emails are they using, are they active, what workspaces are they in, and what channels? Slack doesn't make this easy in their UI at all, let alone our other tools.
Additionally, with many workspaces in Slack Enterprise grid comes many channels. Channels that can span multiple workspaces. Channels that can be connected directly with customers and ones that can be filled with guests. With over 10,000 channels, both active and archived, we'd love to understand stats on those channels and build tools to manage, archive, and adjust those channels. Add channels with customers to CRM's, create channel lists to update with product changes, collect feedback directly from our user and attribute that back and more.
At Current, Fivetran's connectors only understand a handful of channels it's manually added to, and only in one workspace. We would have to connect each of our dozens of workspaces to Fivetran manually, then dedupe that data. Not to mention there would be holes in that data. In enterprise grid, DM's and Group DM's don't exist in any one workspace, they are their own area.
If you have questions about how many customers you have on the grid, you can go to orgname.enterprise.slack.com, for example, hackerone.enterprise.slack.com.
Lastly, I understand that some of this may seem a bit confusing, or unclear. I'm more than happy to spend time going over some of the nuances of enterprise grid, slack's own tools, and what useful data we would like to scrape from this
Thank you.
-
Official comment
Hi Zander
Thank you for the feature request and the detailed information. I have sent an email to understand your use case better.Best
Sandeep -
+1
-
+1
Please sign in to leave a comment.
Comments
3 comments