I just updated the slack plugin on our instance to the latest version ( compare versions ), and it appears the /discourse slack commands are now broken: Here’s what I see in the logs on our instance: Started POST "/slack/command" for 52.91.184.228 at 2017-04-08 15:07:59 +0000 Processing by Discourse…

@tgxworld We should skip before_filter redirect_to_login_if_required here?

Yup I think I removed one of the monkey patches. For the /command path, we need to skip everything because the only authentication we need to do is to check if the Slack token is valid.

my understanding of @vinothkannans suggestion appears to work in a quick test. I’ll let you do what makes the most sense rather than PR it, though.

Thanks for reporting @mcwumbly . I’ve fixed it in https://github.com/discourse/discourse-slack-official/commit/c7ce5722f041253ef0a2ee98a74303ac99b4ae8b and added a test case for it. I’ve been involved in refactoring of the plugin but without existing test cases, there is a higher chance of me break…

Slack command integration broken in official discourse slack plugin

Product Support

david (David Taylor) April 8, 2017, 4:21pm 7

This is exactly what I’ve done in my Telegram plugin (which is very similar to slack in the way the webhooks work). If there’s a better solution I’d be interested to know!

Topic		Replies	Views
Getting 422_client_error when using slash commands in private channels Product Support chat-integration	2	3720	April 4, 2018
Set up Slack notifications using the discourse-chat-integration plugin Integrations chat-integration , how-to	106	36134	June 1, 2026
Topics do not appear in the specified Slack channel Product Support chat-integration	8	4352	April 5, 2018
Help configuring Slack Discourse plugin Product Support	18	5119	September 30, 2019
`/discourse post` command hangs on "Loading the transcript..." Product Support chat-integration	5	746	March 6, 2021

Slack command integration broken in official discourse slack plugin

Related topics