Is there any difference between the Action Hub Slack integration and the older Slackbot set up?

[jamie_davidson]

Knowledge Drop

Last tested: Aug 12, 2020
 

​

Yes - a few differences. The following capabilities are available as part of the overall Slack integration.

1) New in-Slack sharing capabilities and slash commands. This provides more link sharing capabilities in Slack and out-of-the-box slash commands such as /looker favorites and /looker folder . More information is available here: https://help.looker.com/hc/en-us/articles/360038292973-Delivering-and-Retrieving-Data-with-the-Slack...​

2) Slack (Beta) - new action in Action Hub that support OAuth. The action sends data from Looker to Slack. For this action, an admin needs to link a workspace to Looker, then users can OAuth. When sending data to Slack, it sends as the user. Content can be sent to public channels, DMs, and private channels. More information is available here: https://help.looker.com/hc/en-us/articles/360038292973-Delivering-and-Retrieving-Data-with-the-Slack...​

3) Slack Attachment (API Token) - existing action in Action Hub that uses an API or bot token. The action sends data from Looker to Slack. For this action, an admin provides an API or bot token during setup. When sending data to Slack, it sends as the API/bot user. Content can only be sent to public channels and DMs.

4) Lookerbot (also referred to as Slackbot). This is a on-premise-hosted and configured app that enables slash commands to query against single-tile dashboards. The user can use services like Heroku to host the service. More information is available here: https://github.com/looker/lookerbot

This content is subject to limited support.