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.
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.