search

slackapi / bolt-python

A framework to build Slack apps using Python
https://slack.dev/bolt-python/
MIT License
1.03k stars 237 forks source link

Slack Bot works in my workspace, but doesn't respond when Installed elsewhere #1050

Closed MarianBzz closed 2 months ago

MarianBzz commented 4 months ago

When attempting to install the Slack bot developed in my workspace into other workspaces, I encounter difficulties in getting it to function correctly, despite accepting the necessary permissions during the installation process.

I've developed a Slack bot using Socket Mode to enable its integration into different workspaces. While the bot performs flawlessly in my workspace following installation and initial setup, I've faced challenges when attempting to replicate its functionality in other workspaces. Despite completing the installation process successfully, the bot fails to respond to commands or execute its intended functionalities.

Steps Taken:

  1. Configured the Slack bot in my workspace following Slack's provided documentation.
  2. Generated required credentials and configured permissions for the bot.
  3. Installed the bot in other workspaces, adhering to the same procedures followed in my workspace, and accepting all necessary permissions during installation.
  4. Despite successful installation, the bot does not respond to commands or perform expected tasks in other workspaces.

Could it be possible to utilize the app in other workspaces with its functionalities while keeping the Socket Mode activated, or should I consider migrating to HTTP? Alternatively, what might be the reason behind its malfunctioning in other workspaces?

Configuration Details: image

image

WilliamBergamin commented 4 months ago

Hi @MarianBzz thanks for writing in 💯

Have you implemented OAuth? In order to install your application in multiple workspaces (distribution), your app needs to be able to store/handle a bot_token for each workspace it is installed in

Here is an example of OAuth and socket mode

github-actions[bot] commented 3 months ago

👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.

github-actions[bot] commented 2 months ago

As this issue has been inactive for more than one month, we will be closing it. Thank you to all the participants! If you would like to raise a related issue, please create a new issue which includes your specific details and references this issue number.