Governed visual editing 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.

Request a demoSign in

Read it. Change it. Account for it.

  • Modular by design.

    Your flow opens as a Pinboard. Each trigger, action and condition is a Pin you can read on its own, on a desk or on a phone.

  • The difference first.

    Describe the change in your own words. FlowPins shows what would be added, changed and removed before a single step is written.

  • Governed from sandbox to deploy.

    Nothing is changed until a person confirms the exact difference. Each confirmation is recorded with who, when and what.

A small change should not take an afternoon of clicking.

Changing a flow usually means opening the designer, finding the step, picking from long lists and filling each field. Afterwards, somebody asks what was changed, and the answer lives in one person’s memory. FlowPins lets you say what you want, shows you exactly what would change, and keeps the record.

Describe. Review. Confirm.

  1. Open

    Open your flow as a Pinboard. Every step is a Pin you can read.

  2. Describe

    Say what should change, in your own words. FlowPins may ask a short question first.

  3. Review

    Read the exact difference: what is added, what is changed, what is removed.

  4. Confirm

    Press “Confirm and deploy”. Nothing is changed until you do.

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 (the trigger).
Pin
One step (an action).
Split Pin
A decision (Condition, Switch).
Loop Pin
A repeat (Apply to each, Until).
Group Pin
Steps kept together (Scope).

You stay in control of every change.

Nothing is changed until you confirm the exact difference. A copy of the flow as it was is stored before the change is written. The assistant can be wrong; that is why you see the difference first.

How FlowPins is governed

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.

For the people who build flows, and the people who answer for them.

  • Makers.

    Analysts, consultants and developers who change cloud flows and would rather describe a change than hunt for a field.

  • Operations leads.

    People who run on these flows and want to read what a flow does, on a phone, without opening a designer.

  • Governance and project offices.

    People who must show what was changed, by whom and when.

Review from where you are.

FlowPins runs in the browser, laid out for a phone first. Read a Pinboard, review a difference and confirm it from your phone. There is nothing to install.

What FlowPins does not do.

It works only with cloud flows in solutions, in environments with Dataverse. It does not run your flow for you. Connections are created by you in Power Automate. A flow that uses premium connectors needs a Power Automate licence that FlowPins does not provide. FlowPins does not delete flows.

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.

Request a demo