Set up Slack notifications using the discourse-chat-integration plugin

[markvanlan]

Digging into the code, it looks like Create post for category and tag changes site setting needs to be enabled for these tag changes to picked up.

Another note, the Tag added to topic rule will not cause a chat message to go out if the topic already contains one of the tags specified in the tags list.
So in this case:

• tags list for the rule is how-to, admin
• the topic is tagged with how-to already
  → you add the admin tag.

No chat message is sent out.

---

I’m wondering if that dropdown option of Tag added to topic should not even show up in the list if the site setting Create post for category and tag changes is disabled. I could see it still being in the list but there being a prominent visual indicator showing that it will have no effect unless the setting is enabled.

Let me know how that works for you!

[yoolivia (Olivia)]

hey @markvanlan

That setting did it. I gotta admit it is super misleading that that setting is there instead of where I would expect it to be which is somewhere in the chat integration section.

Regardless will keep that in mind, thanks for the help!

[sedghi (Alireza)]

We have started using this plugin which works great

e.g., jumpToCenter is not working in new segmentation mode - Support - Open Health Imaging Foundation

My question is, whether there is a setting that I can hide usernames? or just say anonymous1 and anonymous2

[David_Aland]

Thanks for a great plugin. Works like a charm.

Not sure if this is the right place for it, but it would be great to be able to customize the messages that are posted to Slack. Having the category, and all the tags, and the username and name all gets a bit wordy and it would be great to be able to customize this.

Thanks again.

[gormus (Osman Gormus)]

I recently started testing this integration, and so far so goood I’m really enjoying it. Thank you for making it available.

Though, I have a couple of questions already:

1. What role does the chat integration discourse username play in this setup? How is this user’s TL affect the integration? Should it be included anywhere in Slack side of the setup?

2. How does this integration affect the overall pageview quota?

perhaps as feature request, if you’d consider;

1. Could the template used for /discourse post {n} command use quotation attributes?

Also, I happen to notice a couple of minor issues too:

1. View in #channel-name on Slack link doesn’t support Slack enterprise URL scheme. The generated link doesn’t open in Slack, or in browser.

2. The Slash command may introduce a conflict causing the /admin/plugins/chat-integration/slack page to break. I need to reproduce and provide you the steps.

[simon]

@gormus

What role does the chat integration discourse username play in this setup?

From the main chat integration docs (Discourse Chat Integration):

@Discourse

Security/Permissions

The site setting “chat integration discourse username” allows you to secure your notifications against leaking private information.

By default the system account is used, which means that there is no restriction on notifications sent. To secure your notifications you should create a non-staff user with appropriate access privileges, and enter its username in the site setting.

If you have “Slash Commands” enabled for your provider, and do not trust every member of the external “Channel”, it is absolutely essential that you set this up to avoid them having access to private categories on your forum.

I think that documentation could use some clarification. It’s been a few years since I used the plugin. From reading the doc’s Security/Permissions section, it’s not immediately clear to me how the chat integration discourse username setting affects the way that notifications are displayed on the chat provider.

@gormus

How does this integration affect the overall pageview quota?

It shouldn’t have an effect on the pageview quota. Discourse post data is sent to the chat provider via the API. When a message related to a Discourse post is read on the chat provider, it isn’t generating a page view on Discourse.