Conversation
|
|
||
| 4. **Subscribe to Events** (Event Subscriptions → Subscribe to bot events) | ||
| - `app_mention` - when someone @-mentions the bot | ||
| - `message.im` - DMs to the bot |
There was a problem hiding this comment.
For DMs to the bot to work, I had to also ensure App Home -> "Allow users to send Slash commands and messages from the messages tab" was ticked. (It was unchecked by default.)
There was a problem hiding this comment.
I will revise the readme with all of the relevant scopes needed, Claude's first guess was wrong, but I've figured it out since. I don't believe slash messages is required but there are more bot scopes needed than were originally figured.
| @@ -0,0 +1 @@ | |||
| # Slack bot application | |||
There was a problem hiding this comment.
Can we delete this file?
There was a problem hiding this comment.
I thought Python modules needed an init.py, even if it's empty, right? If you can delete it and everything still works fine and no linters complain, go for it.
I am assuming this relates to the file-structure. Aside from a minimal re-organizing, I don't see any glaring issues with this extension.
This works locally, but I haven't been able to get it to work on dogfood. I see the ellipses forever instead of a reply. 
@nealrichardson Im happy to pick this up if you'd like me to make the changes I've noted above. |
That's due to a bug in Connect where Shiny websocket setup doesn't happen if you deploy it as
That would be fantastic, thank you. I'll bring over the README edits I mentioned but if you could handle the rest that would be great. |
2 participants
I haven't done all of the extension-y things yet but wanted to push this up. Runs a Slack Bot on Connect, with a chat interface in the web version.