Even though we see all kinds of teams using Flowdock these days – from execs to customer support – GitHub is still, by far, the most popular Flowdock integration. We are huge fans of it on the Flowdock team as our software development life revolves around pull requests.

We like to think that the GitHub integration has done an awesome job of giving you an idea of what’s happening in GitHub at any given time. But when you’ve wanted to see the state and history of a specific pull request, you’ve had to jump over to GitHub. Not a big deal, but when you’re in state of flow, every second of concentration counts.

Enter grouped inbox

Pull request in Flowdock team inbox

With the new version of the GitHub integration (we already released a similar upgrade for our Zendesk integration), you get to see the full picture of a specific PR, and discuss it as a whole. It reduces noise and increases cohesion in the team inbox.

Create and assign PRs from Flowdock

Flowdock GitHub pull request assign to me

What’s more, our new concept of team inbox actions allow you to interact with GitHub directly from Flowdock: you can create PRs and assign them to yourself. Flowdock isn’t trying to replace GitHub’s excellent pull request UI – instead, we’re determined to offer ways to make teams’ workflows faster by allowing them to perform simple, common actions right from within Flowdock.

Turn it on today!

To start using the new integration, there are a couple of simple steps:

  • If you’ve already connected GitHub repositories to your flow, you will see a deprecation warning in your Inbox Settings. Follow the instructions to upgrade to the new version.
  • Otherwise, open your flow’s Inbox Settings and add a new GitHub source. You’ll start using the new integration automatically.

The setup process will ask you to grant Flowdock access to your GitHub repositories. This is used to get a list of your repositories, for setting up webhooks, and for the inbox actions. We’ve had some good early feedback from customers saying that they need to be able to set up the integration without exposing access to their GitHub repositories. If you’re one of them, fear not: we are currently in the process of coming up with a manual setup process that doesn’t require such rights.

Addendum, February 10th 2015: It is now possible to configure your GitHub webhooks manually. Read the instructions on how to set them up.

For integration partners

Is your product on the growing list of Flowdock integrations (80+ today)? We’re sure your customers would love to see these new features (grouped events, inbox actions) in your integration. Take a look at our new integration guide for instructions on how to get started.

If you have any feedback about the new GitHub integration or the integration guide, contact us at support@flowdock.com or on Twitter.