# Slack plugin: automatically subscribe a channel to updates on a topic when link is shared

**URL:** <https://meta.discourse.org/t/slack-plugin-automatically-subscribe-a-channel-to-updates-on-a-topic-when-link-is-shared/56520>\
**Category:** Feature\
**Created:** [28.Январь.2017 16:30:20 UTC](https://meta.discourse.org/t/slack-plugin-automatically-subscribe-a-channel-to-updates-on-a-topic-when-link-is-shared/56520 "2017-01-28T16:30:20Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [02.Февраль.2017 15:11:22 UTC](https://meta.discourse.org/t/slack-plugin-automatically-subscribe-a-channel-to-updates-on-a-topic-when-link-is-shared/56520/5 "2017-02-02T15:11:22Z")

</div>

I was thinking it would follow the design established already for categories, using the `/slash-command`

So it’d be something like:

```plaintext
/discourse [watch|follow|mute|help|status] [category|tag|all]

```

Whether tags need to be namespaced or not is something I don’t personally feel too strongly about. On the one hand, the plugin could just infer it for the user, saving them from having to specify things explicitly. There would be the edge-case of a tag that also exists as a category, in which case, a simple “category wins” rule could be put in place. Alternatively, we could require something like this:

```plaintext
/discourse [watch|follow|mute|help|status] [category|tag:name|all]

```

So to subscribe to the “teapot” category, I would do:

```plaintext
/discourse watch teapot

```

And to subscribe to the “teapot” tag, I would do this instead:

```plaintext
/discourse watch tag:teapot

```

---

_[View the full topic](https://meta.discourse.org/t/slack-plugin-automatically-subscribe-a-channel-to-updates-on-a-topic-when-link-is-shared/56520)._