Slack
Slack connects one workspace per login through go.mau.fi/mautrix-slack (v0.2611.0, SlackConnector). Connect multiple workspaces as separate Slack accounts.
| Property | Value |
|---|---|
| Network ID | slack |
| Maturity | Experimental |
| Terms risk | Yes (browser token/email flows act as an unofficial client; workspace admins can see active sessions; Slack app bot flow uses the official API) |
| Operator setup | None |
| New chats from | Existing contacts |
Implementation status
Section titled “Implementation status”- Implemented: Browser sign-in (
token), email code (email), and Slack app bot (app) flows, workspaces asspaceparents with channels/group DMs/DMs underneath, threads (threadRoot+ turning Trioditis replies into Slack thread replies), edits, deletions, Unicode & shortcode reactions (custom_emoji_reactions: falseto avoid deadmxc://links), media up to 50 MiB, PostgreSQL array wrapper fix (slackdb.PostgresArrayWrapper = pq.Array), and backfill. - Remaining: Live end-to-end verification across workspaces, distinguishing
channelvs.groupchat kinds, andselectfield options for multi-workspace email sign-in.
How to connect
Section titled “How to connect”- Sign in on slack.com (
token, recommended): Sign in via the sign-in browser—Trioditis automatically selects “use Slack in your browser”, collects yourxoxc-token andd(xoxd-) cookie, and completes sign-in.- Manual fallback: Open
https://app.slack.com/clientin a private browser window, extract yourxoxc-token fromlocalStorage.localConfig_v2in DevTools Console, copy thedcookie from Application/Storage → Cookies, paste both into Paste cookies instead, and close the window without signing out.
- Manual fallback: Open
- Email code (
email): Enter your email and the 6-character code Slack sends (plus 2FA if required). - Slack app (
app): For workspaces you administer, create a Socket Mode app frommautrix-slack’s manifest and provide thexoxb-bot token andxapp-app-level token. (Bridges only what the bot can access and sends as the bot—not your personal DMs.)
Logging out in Trioditis actively signs out the Slack session (auth.signout).
Unsupported & known limits
Section titled “Unsupported & known limits”- Channels map as
group: The bridge host currently maps both Slack channels and group DMs toChatKind: 'group'(with the workspacespaceasparentPortalId) rather than'channel'. - Multi-workspace email sign-in & CAPTCHAs: The login protocol does not yet pass
selectfield options for picking among multiple workspaces during theemailflow (usetokeninstead). Email-flow CAPTCHAs only work whenlogin-browseris running and remain untested live. - Custom emoji images: Custom emoji reactions arrive as
:shortcode:text. Inline custom emoji in message HTML reference expiredmxc://URIs with the shortcode asalttext. - Voice clip conversion: Without
ffmpegin the container, Slack voice clips arrive in Slack’s native format rather than Ogg/Opus. - Workspace edit/delete policies & Enterprise Grid: Edits/deletes respect workspace restrictions; Enterprise Grid is untested.
What’s stored in plaintext
Section titled “What’s stored in plaintext”Beyond bridgev2’s shared tables:
- No message bodies stored by the connector.
user_login: Workspace name, email, and live session tokens (xoxc-/dcookie or bot tokens; cleared on logout).emojitable: Workspace custom emoji shortcodes and Slack CDN URLs (pruned automatically as emoji are deleted).- Login step instructions: On SSO/error responses during
emailflow, Slack’s error text may include the workspace name.