-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any plan to change to rtm.connect() ? #209
Comments
Thank you for your hard work @lins05 I really enjoyed your slackbot. |
can you explain a bit about rtm.connect ? |
@lucywang000 Slackbot uses rtm.start() to initiate the slack.com API. Which gathers a bunch of info upon start, this is fine for basic workspaces. However for Enterprise Workspaces rtm.start is not allowed and rtm.connect is recommended by slack, which is more specific in regards of the information the bot its requesting. Causing slackbot to get a 500 error when attempting to connect to an Enterprise workspace. Here's slack's doc on it https://api.slack.com/rtm#connecting_with_rtm.connect_vs._rtm.start Ive tried to change rtm.start to rtm.connect, and it connects to slack, but there's some user, channel, group, etc parsing that needs quite a bit of polishing up. |
Should switch over to using slack_sdk for talking to the slack API. |
Thanks all for the discussion. This is fixed in bfdbef9. |
I used this bot for a while, its an awesome project, however not usable with Slack Enterprise as it requires rtm.connect()
The text was updated successfully, but these errors were encountered: