This is a guest blog post by Mikael Roos of Flowdock, a tool that adds a communication layer to Confluence and your other existing tools.

Anyone familiar with Confluence knows that it’s a great tool to create content, share it with others andcollaborate. They also know the problem with staying up to date with all the updates to the content that lives in the wiki. The standard way of addressing this problem is email notifications. However, your inbox is already busy. As a result chances are no one notices the brilliant ideas you’ve taken the time to share in Confluence.

Get Fast and Productive with Flowdock

Flowdock is a tool for teams’ conversations. Like any real conversation, they happen in real time. Your team is always available for discussions no matter where you or they are. You can even keep track of conversations that happen while you’re gone.

Continue to use all your favorite tools and make them better by bringing your actions into the conversation in Flowdock. Updates from your issue tracker, changes from your version control system, deployments, and most importantly activity from your wiki – they’re all a big part of the working conversation. All these events can go unnoticed, and sometimes need to be repeated to attract attention. With Flowdock, your team will react in seconds.

Resurrect Your Ideas

When you install the Flowdock for Confluence plugin and direct the wiki changes to your Flowdock flow, you give those great ideas a whole second life. The ideas and their progress are piped into a place where discussion is ongoing, where they become new topics of conversation, and each new page and later change gets a checkup and a chance for cultivation.

Consider a Confluence page describing your office network. Let’s say something changed, and someone updates the page. Everyone can immediately see the change and comment on it, making these back-and-forth exchanges happen when the change happens and not hours or days later.

Consider another Confluence page, perhaps a specification for an API. As you are planning the API and talking about it in Flowdock, you go and make an update to the spec. This action seamlessly becomes a part of the conversation in Flowdock, posting the details of the update to your flow. This is a huge time saver and makes the planning process more compact and manageable. And your team members become more active Confluence users — a key point in the productive use of a wiki.

Try it Today

Follow these steps to get started with Flowdock and Confluence:

  1. Sign up in Flowdock
  2. Install the Confluence plugin
  3. Configure the integration

Jira and BitBucket Integration On the Way

The Confluence plugin marked the first milestone in the integration roadmap for Flowdock and Atlassian products. Then there was bitbucket — imagine making code changes a part of the conversation, too. The next one is a real no-brainer, Jira. Until then, enjoy your real time wiki!

Flowdock: A Communication Layer for Confluence...