For Power Automate cloud flows

Read, fix and ship every flow without the guesswork.

A free Windows app to read any flow as a diagram, edit it safely in DEV, grade it A to F, find the failures hidden in Succeeded runs and review every change before it reaches your environment.

Download for Windows

{x}

Set variable - varTotalin Condition › True

Value

@add(variables('varTotal'), body('Get_order')?['amount'])

Variables

varTotal integer

Initialize variable - varTotaltop level

declared

Set variable - varTotalin Condition › True

set

Start an approvalin Condition › True

read

One window for the whole life of a flow

01ReadAny flow as a diagram, with its variables and a search across every step.
02EditSteps from a catalog, forms and dynamic content. Saved only to DEV.
03GradeA to F on speed, resources, reliability and security, with the fix.
04DebugThe failed runs, the steps that broke and the parent that called them.
05ReviewEvery edit as a diff, checked, then deployed back. Or reverted.

Hexa Studio in 77 secondsSQL · Flows · Flow runs · Flow tasks · REST builder · Web resources

01 · Read

Read a flow like the person who built it.

Designer
Steps in the order they run. Conditions and switches as columns, scopes and loops you can fold.
Variables
Where each variable is declared, changed and read, with a warning when a parallel loop changes it.
Search
Ctrl+F across step names, connectors and settings. Matches light up, the rest steps back.

02 · Edit

Change a flow without opening the portal. Or breaking production.

Add steps from a catalog, fill them in with forms and dynamic content, and validate before anything is saved. Saving works only on connections tagged DEV, after you review the changes.

List rows - Order linesDataverse · List rows

ParametersSettingsCode

Table name

Order lines salesorderdetail

Filter rows

_salesorderid_value eqDVOrder

Dynamic content · When a row is added

Order salesorderid

Order number ordernumber

Customer _customerid_value

Select columns

quantity,priceperunit

Run after Get a row - Account is successful

Forms for the steps you use: Condition, Switch, loops, Scope, variables, Parse JSON, Select, HTTP, child flows and Dataverse rows, with Run after and secure inputs.
Dynamic content with /: Type a slash in any field for values from earlier steps, or open Insert expression with the function list and a syntax check.
Validate, then save to DEV: Missing settings, broken expressions and the wrong connection reference are caught first. Split view keeps the JSON in step.

03 · Grade

Know what a flow will cost you before it runs a thousand times.

Analysis grades every flow from A to F, estimates the actions it uses per run and lists each finding with the step it's on and how to fix it.

High
No error handling
Nothing runs when the ERP call fails. Wrap the steps in a Scope and add a Catch that runs after it fails or times out.
HTTP - Post to ERP Open in Designer
Medium
A secret in plain inputs
The API key shows in run history to anyone who can open the run. Turn on Secure inputs.
HTTP - Post to ERP Open in Designer
Medium
Loop runs one item at a time
The iterations don't depend on each other. Turn on concurrency in Settings.
Apply to each - line Open in Designer
Low
Every column is returned
Select only the columns the flow reads.
Get a row - Account Open in Designer

Rules based on Cloud Flow Analyzer (MIT).

04 · Debug

Find the failures. Even the ones inside a Succeeded run.

Run history for every flow in a solution. See which flows fail most, follow a failed child flow up to the run that called it, and open any run step by step.

Runs1,847in the last 24 hours

Failed633.4% of runs

Flows with failures4of 38 that ran

FailedOther runs

1 PM1 AMnow

FlowFailedFail rateLast failure

Sync orders to ERP384.2%8 min ago

Validate shipping address173.7%8 min ago

Nightly invoice export625%9 h ago

Notify account owner21.1%3 h ago

Every step of a run: As a diagram or a list, with status, duration, the error and its inputs and outputs. Loops show each repetition.
Find runs by a value: A PO number or an email, searched in the run data over a time window.
Where a Catch ran: The runs that ended Succeeded only because an error handler caught the failure.

05 · Review

Hand a flow to Claude. See every change before it ships.

Check the flows of one task out into a folder of their own. Whoever edits them, you, a teammate or Claude Code, each save is compared with the original and with the cloud.

HexaTasks › TASK-482

CLAUDE.mdthe task, the rules
task.json
flows
Invoice-Sync__3f2a9c1e/definition.jsonsaved
Notify-approvers__81bd04aa/definition.json
.hexa/baselinethe originals

PS TASK-482> claude
Editing Invoice-Sync__3f2a9c1e/definition.json…

Baseline, DEV when addedWorking copy, saved just now

What changed · List invoice lines

inputs › parameters › $filter

- _invoiceid_value eq @{…invoiceid} + _invoiceid_value eq @{…invoiceid} and statecode eq 0

Checks

Nothing looks broken.

New connection reference shared_office365, it has to exist in DEV.

Only the flows you were given: Add them from the task or with Add to task in Flows. Each one is read from the environment as its baseline.
Any two versions, side by side: The original, the edited file, the cloud now and every earlier version, as JSON or drawn like the designer.
Checks, then deploy: Missing actions, broken runAfter, connection references. Then deploy the reviewed version, or an earlier one to revert, back to DEV.

And the rest

Your Dataverse toolbox, in the same window as your flows.

Each tool reads the environment you already have open. Nothing is written until you review it and say so.

Press Ctrl K to jump to any table, flow or tool.

Data

SQL: Query any table in T-SQL, even the big ones: rows stream in as they land. Writes show how many records change and wait for your OK.
REST builder: Web API requests and FetchXML with pickers that know your tables, then copy them as Xrm.WebApi, fetch, C# or a flow action.

Desktop flows

RPA, read only: The desktop flows of an environment with their inputs and outputs, their runs and errors, and the machines that run them.

Monitoring

Plug-in traces: The trace log, newest first. Filter by class, message or table and follow one execution chain.
System jobs: Async plug-ins, workflows and imports, with their status and the reason they failed.

Configuration

Plug-in steps: Assemblies, steps and images by assembly or by table. Microsoft's stay hidden until you ask.
Dependencies: What blocks deleting a table or column, including the plug-in steps and flows Dataverse doesn't track.
Security: A user's real privileges across every role and team, two roles side by side, and why someone can or can't open a record.

Customization

Web resources: Edit JavaScript, HTML and CSS in place. Before anything is saved you see the diff, then save and publish in one step.

CContoso, FFabrikam and NNorthwind. All signed in.

One project per tenant, each with its own Microsoft sign-in and environments. Switching asks first, and production is marked in red.

About Hexa Studio

Hexa Studio is founded and developed by Truong Tan Dat, a Power Platform and Dataverse developer based in Ho Chi Minh City, Vietnam. It brings flows, web resources and the Dataverse Web API together in one fast desktop app, so makers and developers can review every change before it reaches their environments.

Company: Hexa StudioOperated by Truong Tan Dat as sole founder. Not yet incorporated.
Location: Ho Chi Minh City, Vietnam
Team: Truong Tan Dat, FounderProduct, engineering and support · LinkedIn
Contact: founder@hexastudio.com.vn
Policies: Privacy Terms Security & data

Running in a minute.

Free for Windows 10 and 11, 64-bit. It updates itself from then on.