@Tris20 this is sick! I’ve only really spoken about the generic use cases above, I’d say. The only two that I have that are on that level that I haven’t written/talked about yet, and haven’t seen anywhere else are:
Status Page Integration
We sync our status page events 1:1 from our status page to a Discourse category, where each status is its own topic. Status events are mirrored in the original post, even posting in chronologically, ascending. We do little things that our users (internal and external) love, like using the Discourse datetime object so it’s always in their local time, mirror the latest status with a tag on that topic, and some other slick ideas we came up with. I actually wish Meta had this feature.
I should really write more about the full integration, because it’s amazing. We round it off by integrating it with the chat integration and Slack (our company chat tool) so when platform status events happen, those Discourse topics get posted to an internal status channel that everyone can follow, but the conversation will ultimately bring them back to our single source of truth: Discourse!
Airtable Sync
We do so much community program management, project management, and automation in Airtable. We came up with an incredible one-way sync between our Discourse user and user group tables from Discourse to Airtable, so we have a 1:1 copy in Airtable with real-time updates.
In Airtable we can create advanced automations on those events (user lifecycle changes, or even things like changing their location, updating their profile, etc. Airtable also lets you sync these tables to other Airtable bases, which is where the real magic happens. We have an Airtable base where we manage our events program, and we not only use the basel-level user table, but then extend it with additional values that are specific to managing that event program.
The value and scale we get out of this integration, I would say, is unprecedentedly the reason how I scaled my community activity so much before I ever hired my first full-time person on community after 3.5 years (@putty 
).
These are some pretty advanced use cases that I guess if others in the enterprise saw them, would probably be like this:
