Governed change for Power Automate
Pin the change. FlowPins writes it.
Describe a change to a Power Automate cloud flow in plain language, review the difference, and deploy it to your environment.
Works with cloud flows in solutions, in environments with Dataverse.
Sign in with your Microsoft work account. There is nothing to install.
What holds for every change
- A person confirms.
Nothing is written to your environment until someone confirms.
- The exact difference first.
You read what is added, changed and removed before a step is written.
- A copy is kept.
The flow as it was is stored before the change is written.
- Microsoft's supported interface.
You sign in with your Microsoft work account.
Changing a flow is the easy part. Knowing what changed is the hard part.
A cloud flow runs approvals, notifications and hand-offs that people depend on. Then somebody edits it in a designer, alone, and the only record is their memory.
Today
- The flow lives in a designer that few people open.
- A change is a series of clicks nobody else sees.
- “What changed last week?” is answered from memory.
- A reviewer has to trust, or rebuild the flow in their head.
With FlowPins
- The flow opens as a Pinboard that the people you choose can read.
- A change is a sentence, then an exact difference.
- Each confirmed change is recorded: who, when and what.
- A reviewer reads the difference and confirms it, or does not.
How it works
From a sentence to a confirmed change.
Six steps. A person is in charge of every one that matters.
Open.
Pick a flow. It opens as a Pinboard, and every step is a Pin you can read.
Describe.
Say what should change, in your own words. FlowPins may ask a short question first.
See the difference.
Read exactly what would be added, changed and removed. Nothing has been written yet.
Confirm.
Press “Confirm and deploy”. Your confirmation covers the difference you saw, and nothing else.
Written, copy kept.
FlowPins stores a copy of the flow as it was, then writes the change to your environment through Microsoft's supported interface.
Read the runs.
Run the flow in Power Automate, then press “Read runs” to see how each run ended.
Before a step is written
The difference is what you confirm.
FlowPins shows a change the way a reviewer wants to read it. What is added. What is changed. What is removed. You confirm that difference and only that difference. If the change is altered afterwards, it has to be confirmed again.
Added. New Pins, marked with a plus sign.
Changed. Pins whose settings or position would change, with the old and the new value side by side.
Removed. Pins that would go, marked with a minus sign.
The assistant can be wrong. That is why you see the difference first.
Say it the way you would say it to a colleague.
No hunting through menus for the right field. Write the change. FlowPins turns it into a difference you can read.
Example
- “Only send the notification when the priority is High.”
- “Rename this Pin to ‘Notify the account owner’.”
- “Wait two days before the reminder goes out.”
- “Move the check for an empty customer to the top.”
If the request is unclear, FlowPins asks before it proposes anything. If it does not recognise a step you ask for, it says so instead of guessing.
The Pinboard
Your flow, as Pins on a board.
Five kinds of Pin cover the shape of a flow. Each keeps the Microsoft term beside it, so nobody has to learn a new language.
Start Pin
What starts the flow.
In Power AutomateTrigger
Pin
One step.
In Power AutomateAction
Split Pin
A decision.
In Power AutomateCondition, Switch
Loop Pin
A repeat.
In Power AutomateApply to each, Until
Group Pin
Steps kept together.
In Power AutomateScope
Open a Pin to read what it does. Read the whole board to see where a flow branches, repeats and ends.
Governance
Built for the person who has to answer for it.
A change to a flow is a change to how your organisation works. FlowPins treats it that way.
A person confirms. FlowPins writes.
The assistant cannot write to your environment. Only a change a person confirmed is written.
Sandbox first.
A production environment stays closed to changes until your organisation switches it on. Each change there needs a second confirmation.
Every change on record.
Who confirmed it, when, and what the difference was. The record stays with the flow's history.
Your organisation only.
Each organisation's data is kept apart from every other's. What a person can read or change depends on the role you give them.
After the change
See how it ran.
Run the flow in Power Automate, then press “Read runs”. FlowPins reads your flow's runs and shows each run's result: status, start, end, duration, and the error code and text if it failed.
FlowPins does not run your flow for you.
For the people who build flows, and the people who answer for them.
Makers.
You know what the flow should do. You would rather describe the change than hunt for the field. Read the difference, confirm it, move on.
IT and Centre of Excellence admins.
You are asked what changed, who changed it and whether production was touched. With FlowPins the answer is on record, and production stays closed until you open it.
Consultants.
You look after flows that belong to someone else. Show the client the difference before it is written, and leave a record of what was confirmed.
Read a flow from where you are.
FlowPins runs in the browser and is laid out for a phone first. Open a Pinboard and read what a flow does without opening a designer. There is nothing to install.
What FlowPins does not do.
Better to read this here than to find out later.
- It works with cloud flows in solutions, in environments with Dataverse. Other flows are outside its scope.
- It does not run your flow for you. You run it in Power Automate.
- It does not create connections. You create them in Power Automate.
- It does not provide Microsoft licences. A flow that uses premium connectors needs a Power Automate licence from Microsoft.
- It does not delete flows.
- It does not write a change that nobody confirmed.
Questions people ask first.
Can it change a flow without me?
No. Only a change a person confirmed is written.
What if the suggestion is wrong?
The assistant can be wrong. That is why you see the exact difference before a step is written, and nothing is changed until you confirm. A copy of the flow as it was is stored before the change is written.
Can we use it on production flows?
FlowPins starts with sandbox environments. A production environment stays closed to changes until your organisation switches it on, and each change there needs a second confirmation.
Is it a Microsoft product?
Microsoft Power Automate is a product of Microsoft. FlowPins is an independent service and is not affiliated with, endorsed by or sponsored by Microsoft.
See it on a flow like yours.
Tell us what your flows do. We will show you FlowPins on a change you would make this week.