How could we improve Flow?

Github Integration

I was looking for best productive tools for our team, and I am really glad that I met FLOW. I love most of features you have but for my developers have complains with FLOW did not support integrate with Github. So I want to know you have a plan, and If you are not I strongly suggest that make a github integration for all developers who like github!

174 votes
Sign in
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Password icon
Signed in as (Sign out)
  • Cody commented  ·   ·  Flag as inappropriate

    What's the status of this integration? Did you drop all plans for it?

  • Tony commented  ·   ·  Flag as inappropriate

    Please make sure it can integrate with Github Enterprise too.

  • Archie K-D commented  ·   ·  Flag as inappropriate

    For GitHub integration I recommend looking at Clubhouse's approach, they create a git branch name automatically based on the task name or id and then allow the card to be moved automatically from different groups based on pushes, pull requests and merges etc! This would be amazing for developers to be able to use for their workflow and save a huge amount of time!

  • Lori commented  ·   ·  Flag as inappropriate

    Will you be requiring the use of github issues? or will you support Flow tasks being connect into the commit workflow?

  • Joel Kesler commented  ·   ·  Flag as inappropriate

    The lack of GitHub and slack integration are large issues that are keeping us on

  • Sindre commented  ·   ·  Flag as inappropriate has pretty awesome integration against GitHub. I don't know how you plan to integrate against GitHub in Flow, but try to make it awesome please.

    Some ideas for initial support:

    - Goal: A custom card type for "GitHub Issues" which state can be modified both via GitHub and via flow and always appear correctly on both systems.
    - Goal: Be able to have project managers rely only on flow, and developers rely on GitHub issue IDs and auto assign/close features based on Git activity. Such as assign tickets automatically and update status based on branch creation (possible with and close ticket automatically based on mentions in Pull-requests and commits (Github feature).

    Implementation ideas:
    - Ability to link a flow project to (a single?) GitHub project.
    - Ability to associate a Github user account to a flow user.
    - Ability to associate a Flow "section" to a GitHub label and/or Github "Project" column.
    - Ability to read/write all information regarding Github "cards" in flow from the GitHub API.
    - Support for linking against GitHub for access to private repos.

  • Josh Jung commented  ·   ·  Flag as inappropriate

    This might be a dealbreaker for our team. Without GitHub integration, having to update everything in two places makes the project management software a frustration rather than a breeze.

  • Andrew Fiorillo commented  ·   ·  Flag as inappropriate

    I'll add my votes for GitHub support. It's been difficult to get our software engineers on board with Flow because they primarily use GitHub to track issues. Having issues linked to commits is a killer feature for them. I end up having to update both issues in GitHub and tasks in Flow if I work on any project with our software engineers (which is 75% of projects).

  • Phuong Nguyen commented  ·   ·  Flag as inappropriate

    Hello Chris,

    I agree with you. Actually, I'm working for Workato ( and I believe we are already in the process of developing some of the integration processes that you mentioned.

    You might want to follow our request topic ( in our Community Forum for updates and be sure to give us your ideas on the scenarios that you have in mind for integration. That will really help to move our development process along.

    I hope this helps! :)

    Full disclosure: I'm working for Workato as a Customer Success Evangelist

  • Chris commented  ·   ·  Flag as inappropriate

    Github & Bitbucket and also Slack integration would be more than perfect. They are the market leaders out there and for every development team out there it would be a perfect combination to have Flow + Github/Bitbucket + Slack. But Github/Bitbucket and Slack integration are also mandatory for many teams. To be honest if it won't be supported in the near future we would consider to switch to a service that offers it like Trello e.g.

Feedback and Knowledge Base