Need to connect a Freenode channel to a room in HipChat? Or want to give customers a simple way to connect to a channel in your Slack team?

Sameroom does that!
Learn more

 Subscribe via RSS

Tag: flowdock

Connecting a Channel in Slack to a Flow in Flowdock

by @abs

It’s hard to put a positive spin on Flowdock these days.

Its Twitter feed in drought, the product has mostly stagnated, and its main flaw—lack of 1-to-1 history search—appears to be on track to celebrate the arrival of 2016, just like it celebrated the arrivals of 2015, 2014, 2013, 2012, 2011, and 2010.

These harsh words said, I hope Flowdock recovers and find its way back to innovation. I want nothing more than a strong and thriving Flowdock—it’s a good product, and the only left in the space that separates the concepts of identity and team membership (I suspect the lack of 1-1 search is a side effect of this).

Getting out of the apparent rut won’t be easy, but not for lack of resources—Flowdock is now owned by CA Technologies, one of the largest software companies in the world.

By the way, we love the old, old Flowdock logo, this one:


As a sign of protest against the new, new one, we’re not going to update it, unless CA’s lawyers come a-knocking.

Now, where was I?

Oh yes, I’m here to show you how to connect Flowdock to Slack. It’s pretty easy, once you’ve got your Flowdock flow and Slack channel ready (create these, if not).

  • Step 1: Sign in with Flowdock and Slack on Sameroom
  • Step 2: On the Open-a-Tube page, choose your Flowdock flow for Side A and Slack channel for Side B *

* Tubes are commutative: A↔B is the same as B↔A.

To manage this Tube, use the Manage Dashboard. To fine-tune how your messages appear on either end of the Tube, or to make the Tube one-directional, configure posting options.

No Access To the Other Side?

If you’re using Flowdock, but the other team is on Slack (or vice versa), you’ll have to create Portal:

  • Step 1: Sign in with Flowdock on Sameroom
  • Step 2: Create a Portal by selecting your flow
  • Step 3: Send the Portal URL to the other team and wait for them to connect

Once the other team connects, you’ll see the resulting Tube on your Manage page. One of the sides will be grayed out—the side owned by the other team.


Slack doesn’t support threaded comments (and I hope it never does), so those will not be relayed from Flowdock to Slack. For other limitations, see Slack and Flowdock sections on our Limitations page.

We’re @sameroomhq on Twitter, if you have any questions or comments about this integration.

This is the History of Chat

Click for timeline

When our colleague Mikl Kurkov suggested we make a timeline of chat services and their protocols, we all thought it was a great idea. (Little did we know how many services we’d find!) Today, we’re releasing the timeline, and it’s fucking scary. The number of chat services in the market is staggering.

(If you know someone who's thinking about starting a chat service, have them look over this timeline first—doing so might save him/her some substantial pain.)

Perhaps most interesting is how, for the most part, the current state of things has nothing to do with the infamous chat wars of the ‘90s. These days, everything’s largely peaceful and folks are playing nice. Most groups have their own vision for what features are best—and want to build the best chat service they can. Many start by looking around for a protocol, realize that few support the features they want to offer, and just roll out their own.

These organizations rarely realize the challenges they produce in doing so—and that they’ll lose users, because their service doesn’t speak to other chat providers. They do what they have to—and, in turn, add to the many dozens of protocols that are in no way interoperable. Until, they plug-in Sameroom (the universal translator for chat protocols), and suddenly their little island is connected to all the other chat services, out there.

Click to download the PDF

The source code for the timeline is freely available on GitHub. If you see any inaccuracies or omissions, feel free to file an issue or send a pull request:

The artwork for this project was expertly executed by (Eric Karjaluoto from smashLAB.

Connecting Skype to Flowdock

By @abs

Before Slack, before HipChat, before team chat became a thing, there was Skype. It was created with the promise of connecting with long-lost relatives in faraway places, by way of fuzzy video and intermittent audio.

It wasn't the first, and it certainly wasn't the perfect solution, but—almost in a form of a side effect—Skype offered a chance for groups to communicate in real-time through text-based chat. This functionality proved so effective, that Skype turned into the de facto business chat tool for a great many companies.

But, as always, something new comes along and people move on to bigger and greater things. However, what do you do with a bigger and greater thing—let’s say Flowdock—if some folks in a particularly active Skype group just won’t hear any of it?

In the perfect world, you'd use a built-in interoperability solution, like XMPP, to connect Flowdock to Skype. But, XMPP is dead and replacements are nascent.

Our Hangouts integration announcement offers additional thoughts on XMPP's history and fate.

Since Skype killed off XMPP support, you can no longer—theoretically, in practice Flowdock never supported XMPP—get Flowdock to interoperate with Skype for free, but you can buy this interoperability, from us. It's relatively affordable and very reliable.

Below, we explain how to connect a conversation in Skype to a flow in Flowdock. Once connected, all messages and files* between the Skype conversation and Flowdock flow will be mirrored, in real-time.

* Actually, files from Flowdock to Skype will not be stored in Skype. Instead, Sameroom will host them for 24 hours. For more info, see Skype limitations.


Make sure you've got a flow in Flowdock ready. Create one, if not. (Same for Skype.) Then, follow these steps:

You can manage the resulting Tube on your Manage dashboard. To fine-tune how message appear on either side of the Tube, see posting options.

Connecting a Room in HipChat to a Flow in Flowdock

By @abs


Workspace chat tools offer a chance for companies to keep all communication in one place, making it possible for colleagues to collaborate in real-time and—ultimately—eradicate the use of internal email.

Once a team is accustomed to real-time communication, it’s painful to go back. Yet, going back is exactly what happens when multiple teams—each using its own chat platform—have to collaborate on a project. This is a common scenario both for large firms and groups working across companies.

Sameroom is one way to help bid adieu to external email and enable teams to move forward together just as fast as they do in isolation.

In this post, we'll show you how to connect a room in HipChat to a flow in Flowdock. Once connected, you can send messages and files between the two platforms, with each team keeping a complete copy of all communication.

Option 1: You're In Both Teams

If you find yourself switching between HipChat and Flowdock, this option is for you. Before proceeding, make sure you've got your HipChat room and Flowdock flow ready—create new ones, if necessary.

  • Step 1: Add you HipChat and Flowdock accounts to Accounts;
  • Step 2: Go to Open-A-Tube page and choose the HipChat room for Side A and Flowdock flow for Side B.

Use the Manage page to configure and control the Tube.

Option 2: You're In One of the Teams

If you use HipChat, but need to establish real-time communication with a team that's using Flowdock, you can share your room with the other team with a Portal.

(Note: if you're using Flowdock, but need to link up with a team on HipChat, the steps are exactly the same.)

Send the Portal URL to the other team and wait for them to connect.

Reach out on Twitter if you have any questions.