# Set up Discord notifications with the discourse-chat-integration plugin
**URL:** https://meta.discourse.org/t/set-up-discord-notifications-with-the-discourse-chat-integration-plugin/66600
**Category:** Integrations
**Tags:** chat-integration, how-to
**Created:** [21 juli 2017 om 15:04 UTC](https://meta.discourse.org/t/set-up-discord-notifications-with-the-discourse-chat-integration-plugin/66600 "2017-07-21T15:04:04Z")
**Posts on this page:** 4
**Page:** 4
### Author:  [@twofoursixeight](https://meta.discourse.org/u/twofoursixeight)
#### Post date: [28 februari 2024 om 17:29 UTC](https://meta.discourse.org/t/set-up-discord-notifications-with-the-discourse-chat-integration-plugin/66600/74 "2024-02-28T17:29:39Z")
> [@david](#):
>
> 1. Paste the “Webhook URL” that you copied earlier, then click Save Channel.
> If you use the Public Test Build app all the webhooks are in this format ` https://ptb.discordapp.com/api/webhooks/` , so remember to delete `ptb.` part from the webhook before save.
>
> > ⚠ **NOTE** : If you receive an error when using the webhook, ensure the domain name is `discordapp.com` instead of `discord.com`.
I’m going to edit the topic with a few changes.
Adding to the following:
- Webhooks are in the format `https://discord.com/api/webhooks/`.
- There is also a Canary version of discord where webhooks are in the format `https://canary.discord.com/api/webhooks/`
- The warning is now redundant as the discord app is now located in [Discord](https://discord.com/app) instead of [https://discordapp.com](https://discordapp.com). [https://discordapp.com](https://discordapp.com) serves as a redirect to the new link
> [@juiceer](#):
>
> So a few suggestions that could clear up this issue, for the next guy who might not do as much trial-and-error as I did:
>
> 1. Update the validator to have “[discordapp.com](http://discordapp.com)” pass and “[discord.com](http://discord.com)” fail
> 2. Update the validator to have both “[discordapp.com](http://discordapp.com)” and “[discord.com](http://discord.com)” pass
> 3. update the verbiage in the instructions to not have that contradictory note.
That definitely clears up some issues for people adding Discord notifications using chat integration. I had just updated the instructions now because of Discord’s latest changes.
For those afraid of steps, there’s only 7 now because the warning counted as a step 🙂
---
### Author:  [@Esenjin\_Asakha](https://meta.discourse.org/u/Esenjin_Asakha)
#### Post date: [8 september 2024 om 22:39 UTC](https://meta.discourse.org/t/set-up-discord-notifications-with-the-discourse-chat-integration-plugin/66600/75 "2024-09-08T22:39:42Z")
Hello, I can’t post Discourse messages in a Discord forum thread. Would you have a solution for me?
I get the error `discoursechatintegration://:ProviderError` when I try to send a test message. (I did add the thread ID at the end, from the address `?thread_id=111111111`). I tried sending test messages with the `discohook.org` tool and had no problems, so I think my settings are fine ?
---
### Author:  [@mcdanlj](https://meta.discourse.org/u/mcdanlj)
#### Post date: [18 februari 2025 om 12:50 UTC](https://meta.discourse.org/t/set-up-discord-notifications-with-the-discourse-chat-integration-plugin/66600/76 "2025-02-18T12:50:59Z")
It looks like [Hashtags are getting a #makeover](https://meta.discourse.org/t/hashtags-are-getting-a-makeover/248866) category references aren’t rendered correctly in this discourse-chat-integration plugin.
E.g.: this comment:
> **[Text engraving inverted](https://forum.makerforums.info/t/text-engraving-inverted/92689/2?u=mcdanlj)**
>
> @drcmarx I moved this to the Meerk40t category for you. If you post in Meerk40t in the first place, then the system alerts Meerk40t developers. However, if a moderator moves it, it doesn’t alert them. It’s a limitation of the integration we use....
was rendered in discord like this:
Note that the category references are rendered as `Category-Name` — literal HTML, and also unbalanced spans.
(Because the content of the message I quote obliquely references this plugin: This was me gently encouraging a new forum user to choose the most specific category, so that this plugin would know to send a notification. I’m not reporting the behavior of not sending notifications to discord when a topic is newly moved into a watched category as a bug; that’s a reasonable limitation IMHO.)
Not a big deal but I thought I’d mention it since I noticed it. ☺
---
### Author:  [@SaraDev](https://meta.discourse.org/u/SaraDev)
#### Post date: [26 februari 2025 om 00:41 UTC](https://meta.discourse.org/t/set-up-discord-notifications-with-the-discourse-chat-integration-plugin/66600/77 "2025-02-26T00:41:55Z")
> [@Esenjin\_Asakha](#):
>
> I can’t post Discourse messages in a Discord forum thread.
This has been fixed as of the following Discourse update:
[https://github.com/discourse/discourse-chat-integration/pull/251](https://github.com/discourse/discourse-chat-integration/pull/251)
Specifically, syncing topics and posts from Discourse to Discord forums via the `chat-integration` plugin should now create a new forum post in Discord.
Note that with this integration, new topics and replies will appear the same in the forum channel, and you will need to open each forum thread to see the post content.
[Previous page](https://meta.discourse.org/t/set-up-discord-notifications-with-the-discourse-chat-integration-plugin/66600.md?page=3)