1. React To Tweets as a Team

First and foremost, you should track whenever someone mentions your brand on Twitter. We use it for example to detect if someone is asking something about us, even when they’re not directly reaching out to us.

This way we can reply quickly, or have an internal chat about the topic.

Secondly, you can follow the Twitter account of your own brand, just to keep up-to-date about when someone from your team has Tweeted something.

To set these up, head on to Team Inbox settings, type in your brand, and click to follow the keyword, type it again, and click to follow the user. You can even filter out any replies and retweets if you like.

2. Subscribe to Google Alerts

Another great way to stay updated about what people are writing about your brand on the web, is using Google Alerts with Flowdock.

To set Google Alerts up with your Flowdock flow, follow these instructions:

1. Get the email address of your flow (you can find it in Team Inbox settings)
2. Go to google.com/alerts
3. IMPORTANT STEP: If you’ve logged in to google, log out! Google lets you choose a custom e-mail address for the alerts only if you’re not logged in
4. Fill in the form: It’s best to start with “All results” and then change it if you’re getting too many results.
   
5. Click Submit
6. A confirmation e-mail should pop up in Team Inbox. Verify the email address by clicking the link in the message.
   

You’re all set and receiving Google Alert notifications. Now you won’t miss what the public is saying about your product or service.

3. Feedback Should Flow To Your Flow

Feedback is super important for any endeavor. Flowdock is a great place to funnel into all feedback. There are 3 great ways to channel feedback to Flowdock.

1. Automatically forward your feedback emails
   If you have a feedback email address (like feedback@yourcompany.com), make sure that all e-mail sent to it, gets also sent to your Flowdock flow. How this can be done depends on your email service provider. If you’re using Google Apps, check out these instructions (section “To add new members”).
2. Feedback forms
   We use a simple feedback form right within the app from which the feedback is sent to our Flowdock flow. To make this happen, it’s often easiest to use any e-mail capable feedback form to send the feedback to your flow. You can pre-tag the feedback either by using a #hashtag in the subject line or by modifying the e-mail address of the flow in the following way: let’s say your Flowdock subdomain is “company”, the name of your flow is “main” and you want feedback to get tagged with the #feedback tag, you can use the e-mail address main+feedback@company.flowdock.com. If you want to code something yourself, or e-mail isn’t a choice, check out the API.
3. Feedback services (UserVoice, Get Satisfaction etc)
   If you’re using a feedback service of some sort, it’s usually easiest to add a user to that service using the email address of the Flowdock flow as the e-mail address of the account. Then just configure the notification settings of the service to suit your needs. We use this approach to work with our own Uservoice page.

Issues, pull requests, wiki updates, and comments are now pushed to Flowdock in addition to commits. We have been using them ourselves, and it has significantly reduced the time it takes to react to a pull request.

The configuration can be a bit of work until GitHub gets its revamped hooks admin out. If you have an existing Flowdock hook in your GitHub repo, you have to poke the GitHub API a bit.

Configuring new hooks don’t require anything special. Just follow the instructions from our help page and you’re done.

1. Create a Hubot user for your Flowdock company.
2. Follow these deployment instructions.

Among the built-in abilities are:

• show a map for an address (“hubot map me …”)
• show an image based on keywords (“hubot image me …”)
• show a youtube video based on keywords (“hubot youtube me …”)
• fetch an image of a person from the web and add mustache to aforementioned picture of said person as demonstrated above, great for Movember (“hubot mustache me …”)

See the rest by saying “hubot help”. There’s tons more you can add yourself in the hubot-scripts repository.

These features also make use of our new link preview feature (currently works with images, YouTube, Google Maps and tweets).

Make Hubot Useful

Hubot can do much more than incite a laugh or two. For example, one of our users, Christopher Castle, has implemented a JIRA issue fetcher, which allows Hubot to list and search JIRA issues assigned to you.

Similar functionality for Pivotal Tracker has been implemented as well, get it here.

Here’s a quick 45-second video showcasing the integration.

Flowdock also has integrations to other Atlassian’s tools such as Confluence and Bitbucket.

Atlassian OnDemand

Atlassian is now launching Atlassian OnDemand. They’re moving their entire product suite to the cloud. Whether you’re looking for hosted issue tracking, agile planning, an enterprise wiki, or source control, they’ve got you covered. Atlassian OnDemand features fully-integrated cloud-based versions of all their most popular development tools to help take you from concept to launch.

Flowdock integration for JIRA is built-in in Atlassian OnDemand. Just sign up to Atlassian OnDemand and follow these instructions.

Google Apps Integration On Both Sides

Atlassian OnDemand also adds Google Apps integration to Atlassian’s products. Amongst the integration features is logging in with your Google Apps account. Since Flowdock already has the support for it, you can get true single sing-on for all three services.

» Check out the brand new Atlassian OnDemand

At Flowdock, we’ve been mulling over user experiences and interface quite a bit lately. A while back, you might have spotted an experiment we did and wrote about in a blog post to remove the dashboard. Well, just now you might have noticed something else. Like the dashboard gone. Yup, we removed it.

Where are the user list and the mentions?!

Check out the top right corner of your screen. There’s a people icon. Click it and you’ll see the user list. The same dropdown now holds your status, and the editing controls for it.

Next, check out the little speech bubble icon. Click it, and you’ll see the mentions list. A badge bubble will emerge when there are unread stuff in there.

So, what’s new then?

Well, we added a third dropdown. All the way in the topmost, rightmost corner, we have the flows dropdown to give you quick access to your other flows. We still recommend you keep all the different flows you actively use open in different tabs at all times. We’re working on a better UI for using several flows at once.

More! We Need More!

Well, we also added full-screen chat. It’s actually pretty cool. When you resize the window narrower and narrower, the chat finally snaps into full-screen mode and the left side collapses. The same thing happens if you drag the chat wide from the middle separator. When widening the window or narrowing the chat, the left side expands. Snappity-snap!

<< Click to enlarge

One more! Please!

Well, we did add color-coding to the speech bubbles which are show in the chat when commenting on Team Inbox items. The colors are coded to the individual Team Inbox items, so it’s much easier to keep track on multiple “threads” of conversation.

That’s it! Let us know how we did in the comments, or via .

Launched in 2007, Style Me Pretty is on a mission to bring chic and sophisticated wedding to the masses.

Bringing in over 500.000 visitors and 13 million page views each month, Style Me Pretty has grown leaps and bounds from its beginnings. The team has expanded from Abby and Tait to about 15 people scattered all over the United States.

Tracking Media inside Flowdock

Keeping the blog up and running and staying on top of all social networks requires a fleet of technical and non-technical staff. They are located all over the United States, yet they work seamlessly together, and they work fast.

How? With Flowdock.

“Flowdock is just quicker, cleaner and better than other tools around!”, Tait says.

On any given day, Style Me Pretty needs to follow up on the hottest trends, see what’s new, and keep Style Me Pretty active on all social networks, like Twitter. To ensure their fingers are constantly on the pulse of what’s new & pretty, Style Me Pretty tracks social media and website activity through Flowdock’s real time notifications – keeping both internal and external communication timely.

All team on the same page

The entire Style Me Pretty team uses Flowdock on a daily basis – keeping people in constant commutation and making all tasks that much more efficient. Editors may ask the tech team for advice, and the tech team can keep everyone updated on any issues that might arise.

Flowdock is used as a 101 tech support channel inside the team – everyone always knows who’s online, and status updates tell who’s working on what.

Another key function is the social aspect. “The team is spread across many states, and by chatting in Flowdock, the team members connect and gather around a “virtual water cooler”", adds Tait.

“Since we started with Flowdock, the team has more than doubled in size. Flowdock has helped us avoid communication hiccups as we grow!”

In their own words, uxebu is not just another web and mobile app developer. Rather, they go head first to tackle mobile challenges of all kinds, from commercial ventures to open source projects.

Uxebu was kicked off in 2008 between 3 guys. Originally from Munich, Germany, the uxebu team has grown into a collection of developers spread across Munich, Amsterdam and Ohio.

To stay on top of their game regardless of timezones, closely-knit teamwork is a must for this agile startup. When it comes to collaboration, uxebu trusts Flowdock’s expertise.

Less email, more conversation

The uxebu team was never a big fan of email. Before entering the world of Flowdock, uxebu relied on Skype and Skype chat. While Flowdock hasn’t eliminated the need for Skype calls, especially with external clients, what has changed is the way the team works together.

In Flowdock, uxebu has created separate flows, or project rooms, for each project they are working on.

“We don’t have all team members working actively on all projects, but still everyone has free access to each project’s information. If I need to follow up on a project in which I don’t have an active role, I can still access the project flow anytime I want to find the update I need”, Wolfram says.

The team discusses the everyday issues and customer updates in a general flow, but project-based flows are all about hard work. Discussion revolves around work-related details, the real techie stuff.

Highlighting the important info

What makes uxebu’s work more efficient, is how they use #tags and @mentions. Working across timezones can create bottlenecks in development and communication, but Flowdock keeps you notified even when you’re asleep.

“When I open Flowdock in the morning, the comments that are important to me get highlighted. Skype just can’t do this!”, says Wolfram. “Skype’s notification was too noisy for me. In Flowdock, I have customized what types of notifications ping me.”

Connecting team members around the clock smooths out the software development process. All work related discussions take place on Flowdock, making it simple for everyone to stay on top of their game.

Version 1!

In the first version we start with a simple API enabling posting new items to Flowdock’s Team Inbox (previously called Influx).
» See the API Docs

We’ve also wrapped up a Ruby Gem to get you going in just seconds if Ruby is your choice of language.
» Check out the Ruby Gem and install it

Example 1: Custom Feedback Form

Here’s a quick example to get you going. Getting user feedback directly to Flowdock is great. You can talk it over quickly with your team and decide what to do.

This Sinatra app shows a feedback form and sends the feedback to your Flowdock flow using the Flowdock API Ruby Gem.

The view:

The Sinatra controller:

Example 2: FogBugz integration (no coding required!)

The Flowdock Influx API is perfect for use with any service which has web hook / url trigger functionality, such as FogBugz.

Simply by configuring the URL Triggers plugin in Fogbugz (means filling out one form), you can get nicely formatted notifications to Flowdock. We’ve created example instructions for FogBugz Cases, but you can get notifications from wiki changes etc by adding small modifications and creating new triggers.

» Check out the instructions

Example 3: Deployment notifications

Check out our new awesome deployment notification scripts using the Flowdock API.

If you implement an integration using the Flowdock API, let us know, and we’ll spread the good word!

Version 2?

What would you like to see in the Flowdock API? Here’s a few initial ideas:

* bots! (Check out the awesome Flowdock bot implementation by the guys at MyNewsDesk).
* fetching messages by tag – slideshow of latest #sketches ?
* Fetching influx messages
* Jabber integration to use Flowdock with other chat clients (See this idea/discussion in our UserVoice)

Let us know what you think via UserVoice or in the comments.

The bottom line is, Flowdock is a team inbox (Influx) with chat. And awesome tagging mechanisms and super-fast search. That got us thinking. Why is it that a dashboard with relatively little content is the first thing users see when we have other more important things to show, like Infux? So we thought, let’s get rid of the dashboard!

» See the entire screen

The dashboard contains elements that are essential for Flowdock users. We need to come up with new places for those functionalities.

1. Recognizability – We use the name of the flow and company as the title of the Dashboard. Even without this experiment, we need to improve the recognizability of the flows, maybe let users add an icon for each flow and show that in the UI as well as use it as a favicon (shown as the browser tab’s icon). We decided to add a drop-down to the chat header which would take you to other flows. When not selected, it could show the name of the flow.
2. Messages for you – The Dashboard lists any messages where someone mentioned your name or added your @username tag. That’s vital information so we need to add it somewhere. We decided to go with a Facebook/Google+ style message dropdown and add it above the chat.
3. User list – The user list needs to be moved as well. We had lengthy discussions wether it’s a must to be able to see the list all the time. The answer we got to was no. We’ll bundle it up with the notifications

Also, we sometimes show system notifications on the Dashboard. Things like, “Install the Google Chrome app” and other stuff. We decided to bundle it up with the new messages dropdown.

One more thing we had to consider was that the Dashboard icon contains the Flowdock logo which gives the whole UI a distinctive Flowdock look. We should either keep the logo there and make sure no one mistakes it for an app icon or just drop it and try to maybe use it in another part of the UI.

The Result

The first sketches showed real promise. We were happy to see the Dashboard gone. There was some massive refactorings required to get the user list and notifications functionalities extracted from the dashboard and into the chat. We worked hard!

Here you can see what we ended up with showing the same elements 1-3 as above. It’s still kind of rough around the edges, but we’re pretty happy with the results of this 1-day dev excercise!

This way the user can focus better on what’s going on by generally always keeping Influx open. We’ll add badges and other visual cues to the new icons to show you how many new notifications you have, how many people are online at the moment etc. The flows dropdown will give you direct access to the Account page as well as logging out.

Looking For Feedback

What do you think? How do you feel about the departure of the Dashboard? Let us know in the comments, via Twitter or . We need your opinions!

Using a new product for the first time is not always a bliss. For us at Flowdock the flow has become a way of life. We eat our on dog food, and love it, but sometimes we can get blinded by our own user experience. On the flip side, feedback is another thing we love. We’ve received lots of it, but now we’re hungry for more. First-timers, we need your help!

We want the first-time user experience in Flowdock to be as seamless as possible. During this sprint, 90% of our team effort focuses on creating a happier first-time user experience. We call this the FUX.

We aim for a blink-of-an-eye, harmonious FUX-experience by:

• clearly communicating “what Flowdock really is”, and
• designing the flow in a way that makes a FUXie say: “this tool is very intuitive and easy to understand”

And all this, in just a blink. If you sign up to Flowdock today, this is how it looks like:

Admittedly, not very clear nor intuitive. We need your advice! Whether you’re a pro or a new-comer on Flowdock, or just want to contribute, let us know how we could improve the FUX -experience.

1. What instructions were missing the first time you entered your flow?
2. What was made difficult to understand?
3. Was it easy to get your team mates on board?
4. Why would you (or not) recommend Flowdock for other teams to use?