# Will Rocket Chat and others get transcript posting?

**URL:** https://meta.discourse.org/t/will-rocket-chat-and-others-get-transcript-posting/95641
**Category:** Feature
**Tags:** chat-integration
**Created:** [August 25, 2018, 7:38pm UTC](https://meta.discourse.org/t/will-rocket-chat-and-others-get-transcript-posting/95641 "2018-08-25T19:38:16Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![maiki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/maiki/32/233950_2.png) [@maiki](https://meta.discourse.org/u/maiki)
#### Post date: [August 25, 2018, 7:38pm UTC](https://meta.discourse.org/t/will-rocket-chat-and-others-get-transcript-posting/95641/1 "2018-08-25T19:38:16Z")

</div>

Continuing the discussion from [Chatroom Integration Plugin (discourse-chat-integration)](https://meta.discourse.org/t/chatroom-integration-plugin-discourse-chat-integration/66522):

> [@Discourse Chat Integrations](https://meta.discourse.org/t/discourse-chat-integrations/66522/1):
>
> If your provider supports transcript posting, you can post your instant messaging history to discourse. This is currently only supported for the Slack provider. Note: You will need to be using the “Access Token” method of connecting to Slack.

Before I get my hopes up, could you speak to how difficult transcript posting functionality is to add, per provider? From the video (which makes the feature _very_ compelling) it seems like it is very Slack-specific. However, it gets a whole column in the feature matrix… is it a matter of arranging the UI in each provider to choose the messages, or is it provider-dependent?

Because if it is a UI-\>bot-\>webhook thing, I will go bug the RocketChat folks. 🙂

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [August 25, 2018, 8:52pm UTC](https://meta.discourse.org/t/will-rocket-chat-and-others-get-transcript-posting/95641/2 "2018-08-25T20:52:36Z")

</div>

> [@maiki](#):
>
> it seems like it is very Slack-specific.

I’m afraid you are correct here. The user interface is entirely slack based, and won’t transfer well to other providers. Some of the server-side code could be re-used, but not everything.

I would estimate adding super basic transcript posting (without much of a UI) for a new provider to be 2-3 days work **minimum** , but probably more than that.

Adding rocket chat transcript support isn’t on our roadmap, but a (well written and tested) pull request would be welcome.