You can see what happens to OS projects that work with WhatsApp, Skype, and some of the other heavily guarded walled gardens -- cease & desist orders, carried out by GitHub.
We have absolutely no interest in joining that list, which unfortunately means the answer - for the time being - is no :(
Actually I don't think so. The main thing the owners of big networks are afraid of is spam.
We provide a ridiculously expensive way to connect, say, Slack to Skype, which is ==great for Skype==, from almost every possible angle. It means Skype users can stay on Skype instead of switching to someone else's Slack team.
In that case great for skype, bad for slack. Someone, somewhere will decide they'd rather force those customers to use their service/client, or else they'd have an open protocol in the first place.
There's a huge compliance problem with working in someone else's Slack team -- you own none of the resulting data and you don't control access on your end.
Email is much better in this way, since everyone gets a copy.
With Sameroom you essentially retain the carbon copy semantics of email, but with real-time collaboration. So, I'd argue that it's great for Slack.
We have absolutely no interest in joining that list, which unfortunately means the answer - for the time being - is no :(