# Discourse Slackdoor Plugin

**URL:** <https://meta.discourse.org/t/discourse-slackdoor-plugin/44632>\
**Category:** Plugin\
**Tags:** deprecated\
**Created:** [May 22, 2016, 8:26pm UTC](https://meta.discourse.org/t/discourse-slackdoor-plugin/44632 "2016-05-22T20:26:22Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![mcwumbly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcwumbly/32/103861_2.png) [@mcwumbly](https://meta.discourse.org/u/mcwumbly)\
**Post date:** [August 17, 2019, 1:38pm UTC](https://meta.discourse.org/t/discourse-slackdoor-plugin/44632/7 "2019-08-17T13:38:04Z")

</div>

This plugin is now deprecated.

I do not plan to maintain or enhance it.

* * *

It still works but with limitations.

In particular:

1. it doesn’t unfurl messages that don’t _start_ with the link (this was always the case).
2. It does not really do what you expect in threads; the message is “unfurled” in the main channel.

In addition, outgoing webhooks are no longer recommended by Slack. They recommend creating a Slack App for this kind of integration now.

Until recently we had been using this plugin in spite of these risks, but just recently decided to uninstall it as it was causing more confusion than benefits.

I’m not aware of any other existing integration that delivers the ability to unfurl messages for private Discourse instances at this time, so folks may continue to find this one useful as is, but doing so comes with the above limitations and the risks that come with using software that is no longer maintained.

There’s an opportunity for someone else to make something that solves this problem in a better way.

* * *

The README and the OP/Wiki above have now been updated accordingly.

---

_[View the full topic](https://meta.discourse.org/t/discourse-slackdoor-plugin/44632)._
