# Integrations between Slack and Discourse

**URL:** <https://discourse.codeforamerica.org/t/integrations-between-slack-and-discourse/1139>\
**Category:** Organizing a Brigade\
**Tags:** information-sharing\
**Created:** [January 11, 2022, 5:07pm UTC](https://discourse.codeforamerica.org/t/integrations-between-slack-and-discourse/1139 "2022-01-11T17:07:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shaunm44](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/shaunm44/32/487_2.png) [@Shaunm44](https://discourse.codeforamerica.org/u/Shaunm44)\
**Post date:** [January 11, 2022, 5:07pm UTC](https://discourse.codeforamerica.org/t/integrations-between-slack-and-discourse/1139/1 "2022-01-11T17:07:11Z")

</div>

To increase how we utilize both Slack and Discourse, one action being proposed is leveraging the existing tools both platforms provide. One of which is that the ability to monitor/ follow categories or tags in specific Slack channels. This helps for updates on Discourse to automatically populate inside of Slack channels that have subscribed for the updates.  
This page is meant to track which channels are tracking which Discourse areas. This effort is not intended to list all Slack channels and all Discourse topics. Instead, it’s meant to start laying the groundwork for active/ popular areas of both platforms to be more closely intertwined.

**Discourse topics to follow**  
Categories

- #announcements
  - #announcements:brigade-congress-content-committee

- #bats (Brigade Action Teams)
- #culture-and-core-values
- #feedback (Questions & Feedback)
- #from-nac
- #organizing-a-brigade
- #priority-action-areas
  - #priority-action-areas:court-notifications
  - #priority-action-areas:rapid-response

- #projects
  - #projects:project-canvases

- #tools

Tags

- #agenda
- #covid-19
- #court-notifications
- #lightningtalk
- #climate
- #climate-change
- #revisioning
- #ndoch
- #rapid-response
- #nac
- #events
- #brigades
- #record-clearance
- #documentation
- #accessibility
- #fundraising
- #voting-rights

**To integrate**  
[List of Slack channels to follow the Discourse topics available]

- TBD

**Done**

- `#network-stewards`
  - follows #organizing-a-brigade and #information-sharing

- `#clean-slate`
  - follows #expungement

---

<div class="post-metadata">

**Author:** ![chris](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/chris/32/10_2.png) [@chris](https://discourse.codeforamerica.org/u/chris)\
**Post date:** [January 12, 2022, 12:12am UTC](https://discourse.codeforamerica.org/t/integrations-between-slack-and-discourse/1139/2 "2022-01-12T00:12:31Z")

</div>

There’s also `#discourse-firehose` for anyone that just wants to see _everything_ 😛

---

<div class="post-metadata">

**Author:** ![mzagaja](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/mzagaja/32/121_2.png) [@mzagaja](https://discourse.codeforamerica.org/u/mzagaja)\
**Post date:** [January 12, 2022, 2:35am UTC](https://discourse.codeforamerica.org/t/integrations-between-slack-and-discourse/1139/3 "2022-01-12T02:35:21Z")

</div>

I think this could be a good way to kick off discussions in Slack when there are relevant threads in Discourse, and also increase awareness of Discourse within these channels. I gave up on the firehose, too much flow for me!

---

<div class="post-metadata">

**Author:** ![Mari](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/mari/32/992_2.png) [@Mari](https://discourse.codeforamerica.org/u/Mari)\
**Post date:** [July 1, 2023, 7:03am UTC](https://discourse.codeforamerica.org/t/integrations-between-slack-and-discourse/1139/4 "2023-07-01T07:03:28Z")

</div>