Integrate your Flow reports where you need them
How many tools and 3rd party platforms does your team use? Maybe you only have a handful, or maybe a library. Either way, you’ve probably dealt with plenty over the years that had a bunch of great functions and use-cases, but refused to play nice with other software, or made reporting streamlined and API access (or lack thereof) impossible to customize to suit your needs. We feel you.
One of the pain points of any new productivity tool is having disconnects between all the different tools and software you’re using to be more productive. Flow REST API enables you to configure integrations reports to be communicated to you and your team in places you already communicate, including Slack, Jira, Domo, email and other communications and workflow tools.
Data that does what you need
Do you like the idea of maximizing your development data by integrating it with your organization’s existing reporting structure?
Flow REST API is a user-friendly web service for pulling raw data from Flow so you can use it how and where you want. Any of the metrics that you can obtain from a Flow report are accessible or easily calculated from the API. While there are plenty of ways to use the API, here are a few examples of things you can do:
Integrate Flow data with another application to create custom dashboards. Services such as Domo can help you create data-rich dashboards to pull KPIs not in the UI, but are unique and important to your needs.enhance the Flow metrics that are most important to your team.
Extract data to create your own dashboards to display Flow and third-party data to keep the proverbial finger on the correct pulse of your work.
Maximize Flow capabilities and create your own features that fit your teams’ specific needs by implementing integrations tools such as Zapier, which can integrate Flow data with almost any applications your software team uses.
Export data from Flow to spreadsheet tools such as Microsoft Excel to perform custom reporting, data manipulation and your own analysis.
You’re free to Slack
Through our Slack integration, you can create your own rules to stay in-the-know on the milestones your team is hitting, daily coding inspiration for your team or individually-based weekly recaps. Want to get more specific on areas you’re looking to focus on? Putting together KPI reports on pull requests, code commits or any other available data takes only a few minutes.
You can create an array of customized rules, which can be team specific or individually based. Whether it’s coding streaks, pull requests or commits, you can keep everyone up-to-date on the ebb and flow of your team’s development, including:
Weekly recaps with all the key KPIs, including code commits, merge commits, opened PR’s, Merged PR’s as well as others.
Active coding days streak counters to keep the team motivated on consistency.
Weekly look-backs on submitted pull requests and which PR’s the team engaged with the most.
Based upon analysis of metrics and work patterns, you can create custom, auto-triggered messages to be sent to a public or individual channel in your company’s Slack workspace.
This is what your Flow Slack Bot messages could look like.
Emails worth opening
Flow also includes a robust email integration that can deliver to your inbox only the information you deem necessary. No messy spreadsheets that refuse to format themselves in email format or raw lines of data smashed together in a lump, just clean visual reports on the KPIs you select.
Whether you want individual daily reports emailed to each engineer on your team, scheduled reports to the whole team at once or something in between, Flow can be customized to your needs.
While the reports you create for email sends are up to you, the organizational data will always stay on the top, so everyone knows the state of the business before they dive into individual or team data below.
Here’s what your email could look like.
Digests delivered on your schedule
Do you want a development digest sent directly to your inbox before your morning cup of coffee?
Just pick the data, time and cadence of your digest, and your team will be on its way to reclaiming their inbox with things they can use. And with email content that is automatically filtered and tailored to each individual’s permissions, every recipient only sees the information they need. For example, if you want your team members to stay focused on their delivery metrics, they will only see their data and the corresponding aggregate team data. Likewise, if your view rights allow organizational data, the Digest Emails will reflect your view rights.
Here’s a quick look at the types of metrics available, and how they will appear in the Digest Emails:
Impact: Account for the complexity or “bigness” of code changes, in a way that goes beyond lines of code.
Impact: Account for the complexity or “bigness” of code changes, in a way that goes beyond lines of code.
Repository focus: Measure which repositories your engineers are utilizing the most and what percentage of work has been done using each hub.
Work focus: Track which development projects are getting the most time from your team.
Most notable commits: Surface information on the most significant code commits, including the developer, the commit description and quantity of files.
Contributors by impact: Highlight the developers with the most commits within the designated time period, including the projects they worked and comparison with the team.
Contributors by impact: Highlight the developers with the most commits within the designated time period, including the projects they worked and comparison with the team.
5 keys to successful organizational design
How do you create an organization that is nimble, flexible and takes a fresh view of team structure? These are the keys to creating and maintaining a successful business that will last the test of time.
Read more8 ways to stand out in your stand-up meetings
Whether you call them stand-ups, scrums, or morning circles, here's some secrets to standing out and helping everyone get the most out of them.
Read moreTechnology in 2025: Prepare your workforce
The key to surviving this new industrial revolution is leading it. That requires two key elements of agile businesses: awareness of disruptive technology and a plan to develop talent that can make the most of it.
Read more