Chat Integration is for using an external chat system together with Discourse — you may be looking for Discourse Chat which adds Chat functionality directly to Discourse.
| Summary | |
| Install Guide |
The Discourse Chat Integration plugin lets you send messages in your preferred chat platform when something happens in Discourse.
Messages can be triggered by:
- New topics
- New replies
- Messages to a group
- Mentions of a group
Functionality by provider
| Provider | Notifications | Slash Commands | Post Transcripts | Threaded Replies |
|---|---|---|---|---|
| Slack | ||||
| Telegram | ||||
| Discord | ||||
| Mattermost | ||||
| Google Chat | ||||
| Matrix (element.io) | ||||
| Zulip | ||||
| Rocket.Chat | ||||
| Gitter | ||||
| Stride | Docs | |||
| Microsoft Teams | ||||
| Basecamp | Docs | |||
| IRC Cloud | Docs | |||
| Flock | Docs | |||
| Webex |
Before you enabling Slash Commands for your provider, make sure to read the Security/Permissions section below!
Configuration
There are three key concepts in this plugin:
- Providers: The chat platform that you’re connecting to (e.g., Slack, Discord, etc.).
- Channels: A single chat area in your platform (e.g., channel, group chat, room, etc.). Each provider can have multiple channels.
- Rules: The instructions for when and how Discourse should send a message to a channel. Each channel can contain multiple rules.
Configuring providers
- Go to Admin > Installed Plugins and ensure that the Chat Integrations plugin is enabled.
- Click Settings.
- Choose the chat platform that you’d like to connect to Discourse.
- For some providers (e.g., Discord), you’ll be directed straight to the next step (channel configuration). Others will ask for special information, which you’ll need to get from your chat platform.
Dedicated setup instructions for chat platforms
- Slack: Set up Slack notifications using the discourse-chat-integration plugin
- Discord: https://meta.discourse.org/t/discord-chat-integration-discord-notifications/171136
- Microsoft Teams: Set up Microsoft Teams notifications using the discourse-chat-integration plugin
- Telegram: Set up Telegram integration using the discourse-chat-integration plugin
- Google Chat: Set up Google Chat notifications using the discourse-chat-integration plugin
- Matrix: Set up Matrix (element.io) notifications using the discourse-chat-integration plugin
- Zulip: Set up Zulip notifications using the chat integration plugin
- Mattermost: Set up Mattermost notifications using the discourse-chat-integration plugin
- Gitter: Set up Gitter notifications using the discourse-chat-integration plugin
- Rocket.Chat: Set up Rocket Chat notifications using the discourse-chat-integration plugin
- GroupMe: Configure Groupme provider with the discourse-chat-integration plugin
- Webex Teams: Set up Webex notifications using the discourse-chat-integration plugin
Configuring channels
Once you have configured a provider, you can now configure channels for that provider. From the Chat Integration plugin page, click Add channel and provide the requested information — typically a webhook URL and/or channel name, depending on the provider.
Configuring rules
After your channel is connected, you can click Create rule to create a new rule for when your community should send a message to your provider channel.
The main components of a rule are:
-
Type: What type of community content should trigger a chat message?
-
Normal: Send chats for topics in the selected category. -
Group message: Send chats when a PM is sent to the selected group. -
Group mention: Send chats when the selected group is mentioned.
-
-
Filter: You can optionally filter the rule so that it only sends chats in certain situations.
-
All posts with threaded replies: Send chats for all posts matching this rule, with replies threaded in the chat platform. This option is not available for all integrations. -
All posts and replies: Send chats for all posts and replies that match this rule. -
First post only: Only send chats for the first post in a topic or message that matches this rule. -
Tag added to topic: When thecreate post for category and tag changessite setting is enabled, send a chat when someone adds adds a tag to a topic. -
Mute: Do not send chats that match this rule. This is useful for carving out an exception to another broader rule.
-
-
Group: If you selected
Group messageorGroup mentionas the Type, select the group whose received PMs / mentions should trigger the chat. -
Category: If you selected
Normalas the Type, optionally select the category that a topic must be posted in to trigger the chat. - Tags: Optionally select one or more tags that matching topics must have at least one of to trigger the chat message.
What happens when there are multiple rules?
Rules are sorted first by type then by the filter:
- Group mentions
- Mute
- All posts and replies
- First post only
- Group messages
- Mute
- All posts and replies
- First post only
- Normal (i.e. topics)
- Mute
- All posts and replies
- First post only
If a post matches multiple rules, the plugin will trigger the first matching rule in the list.
For example, with the following rules
| Filter | Category | Tags |
|---|---|---|
| All posts and replies | Mentions of: @team
|
(all tags) |
| Mute | Support | (all tags) |
| First post only | Support | unsupported-install |
| All posts and replies | (all categories) | (all tags) |
Notifications would be triggered for:
- A post in Customization > Plugin
- A post in Support mentioning
@team
…but not for:
- A post in Support
- A post in Support with tag unsupported-install
Security / Permissions
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 chat integration discourse username setting.
Slash Commands
If your provider supports slash commands, you can manage rules from within your chat interface. Each provider varies slightly in syntax, but in general they follow a similar structure. (Note that at this time, only the Slack integration implements threads.)
The commands available are
Posting a transcript
If your provider supports transcript posting, you can post your instant messaging history to discourse. This is currently only supported for the Slack provider. Note: You will need to be using the “Access Token” method of connecting to Slack.
Send /discourse post to see the interface. The plugin will try and “guess” where your current conversation starts, by looking for a gap in the message history of more than 3 minutes.
Alternatively, you can specify a number of posts after the command, or a URL to the first message.
To load a transcript for a Slack thread, you can use /discourse post thread {url}, where {url} is the permalink of the first message in the thread. For example:
/discourse post thread https://<slackname>.slack.com/archives/C6029G78F/p1522952993000017
Alternatively, you can use /discourse post with a thread-specific permalink like this:
/discourse post https://foo.slack.com/archives/G49KKS6AX/p1523062012000911?thread_ts=1523091738.000088&cid=G49KKS6AC
In both cases the “first/last message” UI is skipped - the entire thread is included in the transcript.
Adding new providers
Option 1: Submit a PR implementing your provider:
Option 2: Use your own plugin:
It is possible for third party plugins to register new “providers”. As an example, I’ve created a provider which sends webhooks to IFTTT. This could be used to automatically publish all posts in a category to facebook… or turn on your light when someone posts in Contribute > Feature… or feed your fish whenever there’s a new Customization > Plugin.
CHANGELOG
TODO
Last edited by @lindsey 2026-04-21T21:14:15Z
Check document
Perform check on document:




