Presenting a roadmap to learning and mastery of Microsoft Flow at Collab365 Microsoft Flow Virtual Summit

All the Flow you can eat!


I managed to squeeze in last minute with a session on “A roadmap to learning and mastery of Microsoft Flow” this is an advanced session aiming to cover a wide range of techniques and pointing out the pitfalls along these milestones.

The session is near the very end of the Flow Virtual Summit. So I hope you would join me live. (As of this post - the Flow Virtual Summit is on right now). If you want to catch the video on demand after the session, you will need to purchase an All Access Pass.

The review of milestones and roadmap is suitable for learning or navigating our learning along Microsoft Flow.

Affiliate Discount for Flow Virtual Summit All-Pass users

Flow Studio is affiliated with Flow Virtual Summit to offer an additional $20 off the first year of your subscription if you have an Flow Virtual Summit All Access Pass. So this is how it will work.

First year - US$80
Subsequent years - US$100

After July, where Flow Studio’s price increases to US$200

First year - US$180
Subsequent years - $200

So if you have purchased an Flow Virtual Summit All-Pass and is interested in purchasing a Flow Studio subscription - let me know!

Enjoy the show

100 Flow-jutsu of the FlowNinja


Upon reaching a numerical significant milestone of 100 FlowNinja flow-lifehacks. I wanted to review the full list and provide that list here for your glorious consumption during bedtime reading.

Some of them have additional detailed blog post, some of them have an detailed YouTube video - some of them have additional videos or blog posts from the community that added more details to the picture we are all painting together.

Some lifehacks are no longer needed, as Flow has gained that ability natively. Sometimes a connector has changed. Sometimes, I’ve rolled the feature into Flow Studio.

So this is a curated list of the lifehacks, the Flow-jutsu of the Flow Ninja. With small amounts of commentary like someone scribbling notes next to old hacks recalling the wisdom (or insanity) at the time.

Enjoy. Read a random one.

Let me know if there’s a specific Flow-lifehack that you liked but wanted a video or a full blog post. I can tell the blog rate is less than 10% of the tweetstorms. And there’s very little YouTube content of these as well. Both are situations I’d like to improve.

# Flow-jutsu URL
1. Wait until Fire Changed HTTP+Webhook
SharePoint Technically when we have double triggers this will make more sense. Imagine every wehbook trigger can become an in-flow webhook action.
2. Convert PDF to DOCX via CloudConvert
3. Path to Flow-zen
4. Change SharePoint Permission via MSGraph
MSGraph Now use Send HTTP To SharePoint
5. Flow to cancel self or other Flows
Custom Connector Feature rolled into Flow Studio
6. Condition on Trigger
Blog Serge Luca
7. Conditional IP Address on Trigger
8. Approval API via custom connection
Custom Connector Feature rolled into Flow Studio
9. Learn Select
10. Two expressions
11. Flow Governance
12. Flow Editor two hacks
13. No hack to celebrate Send HTTP to SharePoint
14. Read Flow Connectors with Flow
15. Meta Flow killing other Flows
Custom Connector Feature rolled into Flow Studio
16. Make document set with slug
17. Make Excel Chart from Graph
18. Batch connector for Teams
19. Copy DocumentSet files
20. Flow Studio Kunai
Flow Studio Flow Studio marked the beginning of my work to make the hacks I do usable by the power user via an easy to use app. Without Flow Studio - many of my hacks requires a developer to integrate.
21. Flow Studio duplicate
22. Flow Studio Cancel all runs
23. Flow to VSTS
24. Flow Studio tags
25. Save Flow to VSTS
26. Infinite Recursion of Fails
27. Read O365 admin center messages
28. Flow Studio filter by Trigger Type/Kind
29. Multiple SharePoint subscriptions set up
30. Trick the Flow Editor about Update Flow action
31. Calling AzureFunction with webhook
32. Resubmit multi-Flow Runs
33. Send iCal
34. Fast init const
35. Use Flow to Site Design and Site Script
36. World Cup from Flow
37. Watch twitter Followers
38. Flow Studio middleware is Flow - github feedback
39. Flow Studio run ID
40. Retrieve 5K+ rows with paging
41. Emojis are valid name
42. RSS ideas
43. Upload binary from PowerApps via Hacked Flow Button
44. Filter string exercise
45. Filter string Xpath translate()
46. Turn on Forms Split On
47. Coalesce() because expression editor broke
48. Please tell my future self to do timesheets
49. Use Flow to process thumbnails as datauri image
50. Flow O365 Azure Event Grid
51. Greasemonkey script for Flow Expression Editor
The script required frequent update each time when Flow designer is changed. It is something I chose not to maintain overtime. Instead, I put my work into Flow Studio's UX which I can control 100%
52. Windows Timeline
53. Make new Flows from definition
54. Create SP shortcut links
55. Large datasets in Excel - after this I advice using MSGraph to talk to Excel
56. HTTP is not Request
57. Hiding variables out of sight
58. Meta designer hack more space
subsequent Flow designer update now uses Monaco editor for Output - Monaco editor does not resize easily when the output panel's height is auto'ed
59. HTML from Markdown
60. Send email with wishing wand
61. Make Flow Button optional
this is now native in the Flow button designer
62. Creating HTML format in custom definition
63. Action tracked properties
64. Custom actions idea
65. Setting variable with value of itself
66. Hack Flow Button arg into date
this is now native in the Flow button designer
67. Sort in Flow
68. EnsureSiteAssetLibrary
69. Split On false
70. Set like status
71. Google sheet to google cal
72. Fast string replacement with 2 select
73. Use Parse JSON to check types
74. Intersection vs filter array
75. Link to current Flow Run
76. MomentJS in Flow
77. For Selected DocumentSet
78. Use ValidateUpdateListItem
79. ExcelRest
80. Stop flow SharePoint self trigger with validateUpdateListItem
81. Battleship Outlook Calendar
82. Group BY CAML
83. Date Projection and let me count the days
84. DecodeUriComponent for new line
85. Black art of calling internal API on swagger
86. For Each via CSV
87. Upload File via Unused Outlook connector
YouTube Chaks
88. SharePoint modified only trigger
89. Auto reply in Github when issue is closed
90. Fix parallel blocks via Edit JSON
91. A power user friendly method of connecting hundreds of sites, lists and libraries to a single Flow
92. Geofence pokemon go
93. When connections break - send email
94. At-mentions in Microsoft Teams
95. Fast sync of SharePoint list via batch
96. Excel variable names
97. Export Email .eml to SharePoint
98. PowerApps Trigger headers
99. Paste snippets from text
100. Thanos Outlook Snap

The Flow Studio journey and July price increase


I wanted to write an update about Flow Studio, my personal journey so far as a single founder, and announce that there will be a price increase at the end of July.


There will be an increase of Flow Studio subscription price to US$200/year after July. All existing subscriptions will be honoured and maintained at existing prices - so this month is the best time to come onboard and support my work Flow Studio.

If you are using Flow Studio - but don’t see enough value to subscribe. That’s fine - Flow Studio is a freemium product and there will always be a free tier. But I think it’d be alright to ask from time to time that you tell me what would be something that may entice you to change your mind? I am highly motivated to solve your needs and … make you a subscriber. :-)

Journey - what does Flow Studio do?

A year ago, friends ask me: John why do you write Flow Studio, what pain are you trying to solve? I said - I have more than 50 Flows. The response I got was weird looks - well John that’s just you, I wouldn’t build a product based on that.

Fast forward to today - hundreds of people have more than 50 Flows. Some people have more than me. If you support a service account that is a co-owner to many people’s Flows: that account has access to hundreds of Flows.

Consider IT that needs to support Thousands of Flows - what tools do they have?

The problem was never “if” the problem was always “when”. The reality is actually “too soon”

Flow Studio started with simply “Flow inventory management” being able to rapidly find, sort, filter and group with #hashtags our Flows in multiple ever-increasing environments.

We read pages of runs for each Flow - so we can answer questions such as “what has been running most recently” and “which Flows has been failing”. These are powerful features that are not available in the Flow maker portal.

We support bulk operations - multi-select runs and cancel. Multi-select flows and disable. Multi-select approvals and reject.

We added Edit JSON so power users has a quick way to dive into the core definition of a Flow and tweak that. You can do find and replace. Search for URLs or just move blocks around.

We added Contextual Runs - so makers can quickly make sense of a sea of runs and find the error they are looking for.

We added Sparklines so makers can get a bird’s eye view of what’s going on.

Admin view lets an user with environment administrator permission to see all the Flows made by people in that environment - invaluable for IT admins wanting a better overview of Flows in their environment. This is also an excellent view for a Service Account with P2 to be used as the owner of Team Flows.

Major Feature: Migrate

The most latest and significant feature is Migrate. We now support copying, updating and migrating a maker’s Flow(s) across different SharePoint sites and Flow environments. This is a one-to-many support that is not going to be available in the Flow maker portal, and something really necessary for SharePoint and Teams professionals. This allows a maker to create one flow, and copy it across one, twenty, fifty sites. We help makers keep them all up to date.

This is the main feature that we are raising the price of Flow Studio on. So if this is something you think you’ll need for half the price - get in now!


I’ve been a consultant for twenty years - and it’s really a dream to be able to take something I do for one customer and take it into a product.

It is also so much hard work - the main struggle is that the feedback loop for a startup is somewhat delayed and at times completely missing. Unlike a coding challenge - there’s no immediate “problem, debug, fix, done”. A business makes a decision and there’s really no idea if that’s the right decision. And there’s no way to find out for months, if ever, that a decision is right or wrong.

The opportunity costs of each decision, what should I be doing instead, what can I do in parallel. All the community work I still love to do so much, but now I wonder if I’m sabotaging my own startup while being distracted.

Distracted. Scary word. Extremely scary for a founder.

Anyway, I keep my sights on the goal. I’m certain the future of automation within Office 365 and across Microsoft is Microsoft Flow. With that in mind - there is no way a tool like Flow Studio isn’t valuable to a maker, and Flow governance isn’t valuable to a business. I intend to make my way towards that goal. I’m hoping you are all behind me, or alongside me, or cheering for me.

Let me know if you want a demo happy to visit in person or remote.

July Price Increase

Flow Studio Pro subscription is currently priced at US$10 per month or US$100 per year. There are two pricing updates that will go live at the end of July:

The price will increase to US$20 per month or US$200 per year. We believe the added value to Flow Studio over the year has dramatically increased its value. We also believe that as more and more makers are using Microsoft Flow - a solution like Flow Studio to help manage, migrate and rapidly troubleshoot Flows is necessary for the maker.

Australian businesses will be charged at AU$300 - this includes the currency conversion rate as well as inclusive GST, an Australian Tax Invoice will be issued. As an Australian I’m aware that we often feel we pay more than usual US prices, I hope we’d find it fair after conversion including GST.

The price increases are something we intend to do over time. As we keep adding features, we will consider raising the prices to match the value. But this is something we do when the value position of Flow Studio is so significant we actually consider the final price still a bargain for makers. Our promise to existing customers is that Flow Studio subscriptions will remain at the price that you signed up for, as a thank you over a much longer period of support from you. Thank you.

Special Offer: Collab365 Microsoft Flow Virtual Summit

I partner’ed up with the folks at Collab365 - running the Microsoft Flow Virtual Summit next week to offer a special Flow Studio deal for All Access Pass members.

Collab365: Microsoft Flow Virtual Summit is free if you can tune in during the live broadcast of the sessions. If you want to watch the recordings afterwards, you need to purchase an All Access Pass.

The All Access Pass also unlocks a serious bundle of discounts for many affiliated products and services. For Flow Studio - you will get $20 off the first year.

It means if you subscribe to Flow Studio (yearly) before end of July through this offer, you will pay $80 for the first year, and $100/year for subsequent years.

I’ll write more in the next blog post about how this would work.


I have a need of something from all of you.

If you have used one of my Flow tips - then I would like you to try - I seriously ask every Flow maker to try this tool and tell me what they’d like to see.

If you aren’t a subscriber, but would consider yourself my customer, friend or supporter - I’m always in need of founder and product feedback, I feel with you, I can indulge myself and directly ask for your feedback.

Please don’t feel pressured into subscribing if you don’t see the value clearly for you. Your feedback on what would make the product valuable to you is equally if not important than subscribing when you don’t feel like you need it.

Let me know in many ways:

I thank you sincerely for reading this whole post all the way through here. I know raising price is tricky, I want to do it for the right reasons, and explain why I’m doing it. Anyway, you have one month!

Release of Flow Studio: Deploy & future Price Increase

We have released Flow Studio v0.1.91 “Flow Studio: Deploy”

This is a super productive feature that we’ve been working on for a while.

You can think of it as “Flow Migrate Wizard”.

There’s a YouTube video showing the feature.

How Does it work?

  • Select one or more of your existing Flows

  • Enter a new name, or select an existing Flow to overwrite

  • Configure text, URL or variable replacements if you need to create variations

  • Run deploy Plan

What are the use cases?

  • Bulk create Flows from a template

  • Keeping child copies of a Flow updated from a master version

  • (Future) Migrate Flows between environments

  • (Future) Migrate Flows between user accounts

  • (Future) Migrate Flows into Solutions

Future Price Increase

Flow Studio currently is US$100 per year or US$10 per month. When Flow Studio: Deploy goes live (we are hoping in two or week’s time), we will be raising the price of Flow Studio to US$200 per year (or US$20 per month).

As a thank you to current subscribers - existing customers before the price increase will remain under current price.

So yes - if you have been thinking about purchasing Flow Studio in the past but needed a nudge, we are adding a great Deploy feature to go with that nudge.

We believe your time building Flows and keeping them up to date is far worth the price increase we are adding to the product.

As always. We couldn’t have done this without our fans.

Thank you for your support. Let us know what features you need.

Flow Studio 1K users - time for a roadmap update


In the past week - total number of Flow Studio users crossed over 1000.

We have 1000 users!

We want to thank you, Flow makers, for your support. When you share a feature you loved, or suggest a feature that was missing or tell me a bug that we’ve never seen before.

We really enjoyed the journey, there is much we didn’t know when we started, but your support made sure we keep going on.

If you don’t know what John does - check out

What’s next in Flow Studio?

It’s perhaps a good time to talk about what’s coming next on the Flow Studio roadmap.

We have been very busy.

Flow Studio

Flow Studio’s key feature today is a better way to manage a maker’s own inventory of Flows, with a suite of tools to help a maker with making more successful flows.

Along the way, makers relied on:

  • #hashtag grouping

  • Sort by failed runs and last modified runs

  • Run sparklines

  • Edit JSON

  • Runs with Context

  • Bulk run resubmit

  • Flow version history

  • Full definition text search

  • … just to list some of our favourite features.


Our next big roadmap milestone is a Flow deployment wizard

  • Create a deployment plan to copy a template Flow, with variable, URL or connection replacements, to a set of destinations.
    Ideally, the target scenario is for 1 Flow to be copied to 50 SharePoint sites.

  • Keep the deployment plan to perform future updates. Because deployment is never a one-off process.

  • We will be able to copy between 1 to many sites

  • Between multiple Flow environments

  • And eventually, between different accounts - for user migration (and even tenants)

This work is progressing, you can support us right now by trying Flow Studio - and reach out and tell us what scenarios you need.

Get started with Flow Studio for free:

Flow Studio for IT

Flow Studio is designed for an individual maker, or even a consulting company creating Flows under a single account. It helps us manage the Flows in that one account.

It turns out, an inventory management tool for an individual maker and a fast way to see the runs immediately, is actually a scaled down version of what an IT management and governance portal needs.

IT wants to know what’s in every maker’s toolbox. What is running across the enterprise. What’s successful and keep them that way, and what’s not successful and needs to be mitigated.

Picture ourselves across the fog of war that is today’s IT - how many Flows are we able to see? Are they successful? If they aren’t successful, do we know? Are they business critical? If they are business critical but not successful… Is that a risk?

To begin to answer all these questions, we think we need to understand the landscape - let’s produce a Map. Is there a way we can get a bird’s eye view of the entire map of Flows across the entire company.

This is a picture of London underground. The FLOWS IN YOUR ORG LOOKS LIKE THIS.

This is a picture of London underground.

Our second roadmap milestone - is to create a governance dashboard.

We want to know

  • All the Flows and the runs, are they successful, are they failing, when have they been last modified?

  • All the Users - who are our Makers, what Flows do they do?

  • All the Systems - what systems do they touch - not just SharePoint, which Site? Not just Exchange - which email account?

    • You can use SharePoint connectors. But you can’t use it on any site URL

    • You can use Exchange connectors. But you can’t use it on certain email addresses

  • All the solutions - we understand

    • Flow solutions (managed and unmanaged)

    • Teams Flows

    • Personal Flows

    • Resource Owner Flows

    • We also understand if a maker is using Flow Studio tags.

  • All the connectors

  • Monitor, Alert Agents, Reports

  • Bring the bulk editing tooling from Flow Studio and scale it to IT

We want to ensure

  • All your business critical processes are automated and monitored

  • Maintain Flow success - we want green ticks across the map

We are in the process of building this out with several partners that has expressed interest. Please do reach out if you think your IT needs this. We are looking out for early pilot companies that wants to see and be on top of the Flows that are being created across their business. We think we have the perfect product you might want to try and build it with us.

Contact us: support @


I leave this one at the end - Flow Studio is supported by a separate business entity Flow Studio Solutions, which is also John’s first company. So, aside from writing all that wonderful code (code is so wonderful), I’m also learning everything that I loved about learning. From the next Australian financial year forward, Flow Studio invoices will come out of a company entity.

There is much uncertainty of what I just don’t know. Sales, tax, marketing, support. My problems have their own problems. Like IT needs a MAP to see their Flows, John also needs a mental map to see his business.

If you feel hey John’s cadence has slowed down - I’m sorry. My efforts are split between several major roadmap milestone features. These are bigger pieces that needs more work to get right before I can push them out the door. Hope you understand.

Reminding myself to be more kind. Scary is the unknown path I have chosen, but I need to remind myself to be more kind, there’s enough stress in the world, I shall not add more.

We hope to bring you the latest in Flow Studio very very soon! Drop us a comment or note about anything!