How it works

One change, start to finish.

A support flow notifies the account owner about every new request. The team wants that only for High priority. Here is that change in FlowPins.

ExampleThe flow on this page is a sample drawn for illustration.

Chapter 1 · Open

Open the flow as a Pinboard.

Sign in with your Microsoft work account and pick the flow. It opens as a Pinboard: the Start Pin at the top, then each step as a Pin, with branches and repeats drawn as they run.

What you seeEvery Pin by name, with the Microsoft term beside it. Open a Pin to read its settings.
What FlowPins does not do hereIt changes nothing. Opening a flow is reading.

Chapter 2 · Describe

Say what should change.

Write the change in your own words: “Only notify the owner when the priority is High. Otherwise wait two days.” Point at a Pin if the change is about one step.

What you seeYour request, and a short question if something is unclear.
What FlowPins does not do hereIt does not guess. If it does not recognise a step you ask for, it says so.

Chapter 3 · See the difference

Read exactly what would change.

FlowPins answers with a difference, not with a new flow to trust. Added Pins carry a plus sign. Changed Pins show the old and the new value. Removed Pins carry a minus sign. The Pinboard shows the same change in place, so you see where it lands.

What you seeTwo Pins added, one Pin moved under “If yes”, nothing removed.
What FlowPins does not do hereNothing has been written. Your flow in Power Automate is as it was.

Chapter 4 · Confirm

Confirm that difference, and only that difference.

Press “Confirm and deploy”. Your confirmation is tied to the exact difference on your screen. If the change is altered after you confirmed, the confirmation no longer counts and the new difference has to be confirmed again.

What you seeWho is confirming, which flow, which environment. In a production environment, a second confirmation.
What FlowPins does not do hereIt does not write a change that nobody confirmed. The assistant cannot write to your environment.

Chapter 5 · Written, copy kept

The change is written. The flow as it was is kept.

First FlowPins stores a copy of the flow as it was. Then it writes the confirmed change to your environment through Microsoft's supported interface. The confirmation is recorded with who, when and what.

What you seeThe change in the flow's history, with the difference that was confirmed.
What FlowPins does not do hereIt does not delete flows.

Chapter 6 · Read the runs

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.

What you seeOne line per run, with its status.
What FlowPins does not do hereIt does not run your flow for you.

Sometimes the right answer is a question, or a no.

A tool that agrees with everything is not a tool you can govern with.

It asks.

When a request can be read two ways, FlowPins asks a short question before it proposes a change.

It says what it does not know.

When you ask for a step it does not recognise, it tells you instead of inventing one.

It waits.

A proposed change stays a proposal until a person confirms it.

It keeps production closed.

Until your organisation switches a production environment on, changes there are not offered.

See it on a flow like yours.

Bring one change you would make this week. We will walk it through with you.