Guide

Start here

Power Automate has two flow designers: the modern one, which opens by default, and the classic one. The extension opens your flows in the designer you choose, and adds its features to the classic designer.

1. Click the extension icon in Chrome's toolbar and choose Classic. Pin the icon first via the puzzle piece, so it stays visible.
2. Open a flow. It opens in the classic designer.
3. Click in a field and open the Expression tab: you see the large editor. That is the first feature below.

Writing expressions

Large expression editor

The expression editor of the classic designer is one line of about 330 pixels. The extension makes it 760 × 200 pixels, with word wrap, so you can read a long expression at once.

Make it your own size

• Drag the purple grip in the bottom-right corner of the editor to change the width and height. The text rewraps while you drag. The first time, a small hint points at it.
• Drag the grip in the bottom-right corner of the popup to make the whole popup taller or wider, on both tabs.
• The size is remembered, also in other tabs and on other computers with Chrome sync.
• Double-click a grip, or select Reset size in the settings window, to go back to 760 × 200.

Switch in the settings window: Large expression editor

Writing expressions

Move or center the popup

Drag the dynamic content and expression popup by the purple handle at the top, so it does not cover the part of the flow you need.

• The popup stays inside the window. The next time it opens, it is back in its normal place.
• Double-click the handle to put it back right away.
• With Center expression popup on, the popup opens in the middle of the window and stays there when its size changes, such as when you switch tabs or drag a grip. Once you drag it, it stays where you drop it.

The handle has no switch. Centering: Center expression popup in the settings window, off by default.

Writing expressions

Function | Dynamic content

In the classic designer, dynamic content and expressions are separate tabs. The extension adds a switch below the editor, like in the modern designer, so you can put dynamic content in an expression without leaving it.

How to use it

1. Open the Expression tab and type the start of your expression, for example concat(.
2. Below the editor, choose Dynamic content.
3. Type in the search box next to OK, for example the name of an action.
4. Click a result: it goes into the expression at the cursor.
5. Press Cmd+Enter or Ctrl+Enter, or select OK.

Good to know

• The search also finds items hidden behind See more, and all outputs of an action when you search for its name.
• The switch remembers your last choice for the next time.
• In a solution, the environment variables are folded at the top of the list. Click the header to show them; a search still finds them.
• Escape clears the search; a second Escape closes the popup.
• The switch and its search box need the Large expression editor. With the small editor, the popup works as Microsoft made it.

Switch in the settings window: Dynamic content search

Writing expressions

Bracket colors

A missing or extra bracket is easy to make in a long expression and hard to find; the designer only says the expression is invalid. The extension colors the brackets, like VS Code.

• Each level of ( ) and [ ] has its own color: blue, green, brown, and then blue again.
• With the cursor next to a bracket, that bracket and its partner get a box.
• A bracket without a partner is red with a wavy underline. Hover over it to see why.
• Brackets inside text between single quotes, such as 'Status (old)', do not count.

Switch in the settings window: Bracket colors

Writing expressions

Format an expression

A long expression on one line is hard to read. Two small buttons next to OK or Update put it over several lines, and back.

1. Type or open an expression in the Expression tab.
2. Select Format. Each argument of a call goes on its own line, indented one step per nested call, when the call has another function in it or is long. A call without other functions in it, such as replace('a', '/', '-'), stays on one line inside another call (the outermost call is always split), and references such as variables('a') and a function of one constant such as string('a') count as values.
3. Select One line to remove the line breaks and indentation again.

• Cmd+Shift+F (Mac) or Ctrl+Shift+F (Windows) in the editor does the same as a toggle: one line becomes formatted, and a formatted expression becomes one line.
• Cmd/Ctrl+Z brings back the text from before.
• Only white space outside text between single quotes changes, so the expression means the same. OK and Update put the expression back on one line first, so the flow always gets it as usual.
• The buttons and the shortcut need the Large expression editor: the small editor has room for one line only.

Indent on Enter

Enter in the large editor works as in a code editor. The new line keeps the indentation of the line you are on, and right after an opening bracket it is indented one step more. Between a pair of brackets, such as replace(|), the closing bracket goes to a line of its own, with the cursor on an indented line in between.

• After 'test', inside the brackets, Enter gives a new line at the same indentation, for the next parameter.
• With the list of suggestions open, Enter picks the suggestion.
• Between single quotes, Enter adds a line break to the text itself, for the rare expression that needs one. It stays when you select OK.

Switches in the settings window: Format expression and Indent on Enter

Writing expressions

Function brackets

Pick a function from the suggestions and its brackets come with it, with the cursor between them: conc and Tab gives concat(|).

• It works with Tab, Enter or a click on the suggestion, and shows the parameters of the function.
• When a bracket already follows the name, the cursor only moves past it.
• true, false and null get no brackets.
• Cmd/Ctrl+Z removes the name and the brackets in one step.

Switch in the settings window: Function brackets

Writing expressions

Copy dynamic content and expressions

Point at dynamic content or an expression in a field and a small bar appears over it: Copy puts it on the clipboard as its expression, such as @{outputs('Compose')}, and Cut also removes it from the field. Paste it into another field and it is a token again; paste it into the Expression tab and the @{} is left out.

• It works in the fields of every action and in the rules of a Condition, Filter array or Do until.
• Cut removes the token the same way as its ×, so Undo in the command bar brings it back.
• In the expression editor, @{outputs('Compose')} and @outputs('Compose') are pasted as outputs('Compose'). Text with more than one @{...}, such as Hi @{a} and @{b}, is pasted as it is.
• The expressions of the Conditions panel of a run and of the Full expressions lines have Copy too.
• In the field of an action, the designer itself copies tokens with the keyboard too: click dynamic content, or select part of the field, and press Cmd/Ctrl+C or Cmd/Ctrl+X. A click on an expression opens it in the expression editor instead, which is where the bar helps.

Switch in the settings window: Copy dynamic content and expressions

Writing expressions

Confirm with the keyboard

Press Cmd+Enter (Mac) or Ctrl+Enter (Windows) in the expression editor or its search box to press OK or Update. Without the extension, the key adds a new line to the expression.

No switch: always on in the classic designer.

Finding your way

Action search

Find any action in a large flow, also inside collapsed loops, conditions and switches, and also by what is inside it, such as a site address, a list name or an expression.

How to use it

1. Select Search in the command bar, next to Flow checker, or press Alt+Shift+F.
2. Type a word. The list shows every action whose name, type or parameters contain it.
3. Click a result, or use the arrow keys and Enter. The designer opens the blocks around it and scrolls it into view.

More in the panel

• Names or Parameters narrows where it searches; Aa matches upper and lower case.
• Find usages lists the actions that use an action's output. For a variable (on Initialize variable, Set variable and the like) it lists the actions that set it and the ones that read it, each with a sets or reads tag. A click on a result of Find usages opens it and outlines every field that uses the action or variable in red for a moment.
• Copy as JSON puts an action on My clipboard, to paste from the + on an arrow, and copies it as JSON for after a page reload or another browser: paste that with Cmd+V in My clipboard of Add an action.
• Outline (the button with the lines at the top of the panel, or Alt+O) shows the flow as a tree with the actions of each block, branch and case indented below it. The arrow before a block folds it, in the panel only, also while searching; a new search starts unfolded. Opening a card on the canvas selects it in the panel too, also when the panel opens afterwards. Press Alt+O again to go back to the list.
• Replace changes typed text in all actions at once, with its own Undo.
• The box before each action selects it, to delete or move several actions at once.
• In a flow run, Failed and Skipped list only those actions.
• Failed in the list is an overview of the errors: one row per stop of Go to error, also per failed iteration of a loop, with the error message below it. Choosing a row switches the loop to that iteration and opens the failed action.

Switch in the settings window: Action search

Finding your way

Review flow

Check a flow for common mistakes that Flow checker does not report, such as no error handling, secrets in the run history or unused variables, and go to each one.

How to use it

1. Open a flow in the classic designer and select Search in the command bar.
2. Select Review at the top of the panel, the clipboard with a check (Alt+V).
3. The panel lists each action with what was found, in the order of the flow. Select one, or use the arrow keys and Enter, to open and outline that action.

What it checks

• Warning: no action runs after a failed or timed-out action anywhere (no Try and Catch); an HTTP action that sends a secret, or a Key Vault secret, without Secure inputs or Secure outputs; an Apply to each that runs in parallel and changes a variable inside; a SharePoint Get items without a Filter Query or Top Count.
• Info: a variable that is never read; a Compose whose output is never used; a block without actions; a SharePoint site address typed in instead of an environment variable; a default name such as Compose 3; a Get items that stops at 100 items without Pagination.

Good to know

• Findings about the whole flow, such as no error handling, stand above the list.
• Warnings below the search box (Alt+W) hides the info findings, such as default names; All findings shows them again.
• The list follows your edits: solve a finding and it disappears. Nothing is changed or saved by the review itself.
• Typing in the search box narrows the findings to matching actions. Review again, or Outline, goes back to the search.

Switch in the settings window: Review flow

Finding your way

Go to error

In a flow run, jump straight to the action that failed, also when it is inside a collapsed scope or loop.

How to use it

1. Open a flow run that has a failed action, in the classic designer.
2. Select Go to error in the command bar, before Resubmit.
3. The designer opens the blocks around the failed action and opens it, so its error shows. It is centered and outlined in red for a moment.

Good to know

• A scope or loop around a failed action shows Failed too. The button skips those and goes to the action that failed itself.
• The button shows how many failed actions there are, such as Go to error (5), and after a click where you are: Go to error 2/5. Each next click goes to the next one, and then back to the first.
• The failed actions inside loop iterations are counted too, before you go there. Only in a very large run can the number still grow after a visit; the tooltip then says so.
• A loop shows one iteration at a time. For a failed Apply to each or Do until, the button switches the loop to the iteration that failed, also in nested loops, and the tooltip names it: "Failed in iteration 157 of 300". Each failed iteration is a stop of its own.

Switch in the settings window: Go to error

Finding your way

Edit action from a run

From a flow run straight to that action in the flow editor, opened and in view.

How to use it

1. Open a flow run in the classic designer and open an action, for example the one that failed.
2. Select Edit in the header of the open card, next to the duration.
3. The flow editor opens with that action opened, centered and outlined in red for a moment.

Good to know

• Cmd+click (macOS) or Ctrl+click, or a middle click, opens the editor in a new tab, so the run stays open.
• In the Search panel of a run, each result has an Edit action button (Alt+E for the selected result), also for an action whose card is closed.
• The editor shows the current version of the flow. When the action was renamed or deleted since the run, a message at the bottom of the page says so.

Switch in the settings window: Edit action from a run

Finding your way

Condition rules in a run

In a flow run, a Condition only says true or false. See which of its rules made it so, with the value of each side in the run.

How to use it

1. Open a flow run in the classic designer and open a Condition.
2. Select Show conditions in the header of its inputs, next to Show raw inputs.
3. Each rule shows on one line, as in the Condition editor: True, False or Unknown, then each side with = value, its value in the run. Hover a field for the whole expression and value.

Good to know

• Power Automate keeps only the overall result, so the rules are worked out again from the run: the outputs of actions and the trigger, the item of an Apply to each, and variables that only Initialize variable and Set variable change, outside loops.
• Unknown comes with its reason, such as utcNow(), a function that is not supported, or two texts that differ only in upper and lower case. A dashed outline means the outcome is the only one that fits the Condition's real result.
• If the worked-out result differs from the real one, the panel says so. The real Expression result always counts.
• Nothing is loaded until you select Show conditions.
• A Filter array has Show conditions in its inputs too. Its rules use item(), so the panel shows one item of From at a time: go through them with ‹ and › or type a number. Each item says Kept or Dropped, as in the run's output.
• All items next to the item number opens a panel on the right with every item of From in one list: Kept or Dropped, a few key fields (first, in bold, the fields the conditions use), and under a dropped item why, in words, such as Age is 12, not greater than 18. Show only kept or dropped items, search their content, open an item's JSON, or select a row to see that item's rules in the card. Esc closes it.
• A Do until has a Conditions bar at the top of its loop. The panel follows the loop's pager: the loop goes on while its condition is false, so each iteration before the last was false and the last one true.

Switch in the settings window: Condition rules in a run

Finding your way

Array sizes in a run

In a flow run, see at a glance how many items an array in the inputs or outputs of an action has.

How to use it

1. Open a flow run in the classic designer and open an action, such as a Compose, Filter array, Select or HTTP.
2. Each array in its inputs and outputs shows its number of items in gray after the [, such as [ 25 items. Arrays deeper in the JSON have one too, such as value in the body of an HTTP call.
3. Show raw inputs and Show raw outputs show the counts as well.

Good to know

• An empty array [] gets no count.
• The counts are not part of the text: copying the JSON copies it without them.
• Only the JSON on the page is read; nothing extra is loaded.

Switch in the settings window: Array sizes in a run

Finding your way

Fold JSON in a run

Fold objects and arrays in the inputs and outputs of a run, so a large JSON shows its outline first.

How to use it

1. Open a flow run in the classic designer and open an action, or click Show raw inputs or Show raw outputs.
2. Each object and array has an arrow before it. Click one to fold that object or array; a folded array keeps its count, such as "Channel Owners": [ 7 items …, and a folded object shows its number of keys.
3. In the raw panel, Fold all folds everything inside the outer object or array, so its keys still show; Unfold all opens everything again.

Good to know

• The JSON always opens unfolded.
• Each item of an array shows its index (0:, 1:, …), also in the inputs and outputs window, so you can find item 1,234 of a long array. Turn it off with Index before array items, under Fold JSON in a run.
• Folding changes only the view; copying copies the whole JSON.

Switch in the settings window: Fold JSON in a run

Finding your way

Inputs and outputs in a window

Put the inputs and outputs of a run action in a window of their own, for instance on a second screen, and keep exploring the flow.

How to use it

1. Open a flow run in the classic designer and open an action.
2. Click Open in window in the header of its Inputs, or at the top of the raw inputs/outputs panel. A window opens with the action's Inputs and Outputs as a JSON tree that folds.
3. The window follows the run: click another action, or page through a loop, and it shows that action or repetition.
4. Click Pin to keep the window on its action. The next Open in window opens a new window that follows, so you can put several actions side by side.

Good to know

• The window opens where you last left it. Copy copies the JSON of the open tab; Cmd/Ctrl+F also finds text in folded parts and opens them.
• The extension reads the inputs and outputs as the designer does, from the run; nothing goes anywhere else.
• Secured inputs and outputs are not shown.

Switch in the settings window: Inputs and outputs in a window

Finding your way

Filter runs

See all runs of a flow in one list, filter and search them, also in what the trigger received, and resubmit or cancel several at once.

How to use it

1. Open the run history of a flow (All runs on the flow's page) and select Filter runs at the right of Run history. On the flow's details page, Filter runs is in the title of the 28-day run history card, before Edit columns.
2. Choose a Status, Started after and Started before, and how many runs to load, then Load runs. The first 1,000 runs load when the panel opens.
3. Click a column header to sort on it, or to filter it: choose a condition, such as contains, equals, is after or is longer than, and type a value. Status has check boxes instead, such as Failed and Running, with the number of runs of each. Active filters show above the table; × removes one. Next to each start time is how long ago the run started, such as (3 min ago) or (5 d ago), as in Power Automate's own run lists.
4. Drag a column header to move the column, and the edge of a header to change its width; a double-click on the edge fits the column to its content. The order and widths are remembered per flow; Reset layout in Columns puts them back and keeps the columns you chose, Reset all also goes back to the standard columns. The search box above the table searches every column.
5. Select Columns to add fields of the trigger outputs as columns, such as ID or DocID of a SharePoint item; their values load by themselves. The properties of an object, also of one passed on as text such as parameters, are listed indented under it, each as a column of its own; the arrow at the right of the object collapses or expands them. Duration, Status and Error can be hidden there too.
6. Select Load trigger content to search in the trigger inputs and outputs too.
7. Tick runs and select Resubmit, or Cancel runs for runs that are still running. The panel asks first. Export CSV saves the rows you see.

In the designer

1. In the classic designer, while you edit the flow or look at a run, select Runs in the command bar, after Search.
2. The runs show next to the canvas, with the run you are looking at marked. Hover a status for the error of a failed run.
3. Click a run to open it. The list opens again with the same filters, so you can go from run to run. Expand shows the whole table, Dock puts it back next to the canvas.

Good to know

• Status and dates are filtered by Power Automate itself, so a flow with many runs loads only what you ask for. Every other filter works on the runs that are loaded.
• Words in a search all have to be found; put a phrase in quotes, such as "not found". Upper and lower case do not matter.
• Loading the trigger content takes one request per run, so it only happens when you select it. Runs with secured inputs and outputs show a –.
• Resubmit starts each run again with the same trigger input, so its actions run again too, such as sending mail.
• The columns you choose are remembered per flow in this browser. Inputs of a manual or Power Apps trigger show with the names you gave them.
• Drag the left edge of the panel to make it wider or narrower; a double-click gives the default width.
• Opening a run from the designer leaves the edit view; save your changes first.

Switch in the settings window: Filter runs

Finding your way

Filter flows

See every flow of your list in one table, without Show more, and filter, sort and search it on any column.

How to use it

1. Open My flows and select Filter flows at the right of the tabs Cloud flows … Shared with me. It works on both tabs.
2. All flows of the tab load at once, 50 at a time, as Power Automate loads them; the count shows above the table. Stop stops it, Load the rest goes on, Load again starts over.
3. The table shows Name, Modified, Created, Status (On, Off or Suspended), Type (Instant, Automated or Scheduled), Trigger, the Connectors the flow uses, Solution (whether it is in a solution, and managed) and Premium (whether the flow needs a premium license, as the diamond after its name says).
4. Click a column header to sort on it or to filter it. Status, Type, Trigger, Connectors, Solution and Premium have check boxes with the number of flows of each, such as all flows that use SharePoint, all that are off, or all premium flows. Name and the dates have a condition, such as contains or is after, and a value. Active filters show above the table; × removes one.
5. The search box searches every column. Click a name to open the flow, ↗ opens it in a new tab.
6. Columns hides or shows columns; drag the edge of a header to make a column wider. Export CSV saves the rows you see.

Good to know

• The flows are loaded with your own sign-in, the same way the page loads them; nothing is changed.
• Words in a search all have to be found; put a phrase in quotes. Upper and lower case do not matter.
• Hidden columns, column widths and the width of the panel are remembered in this browser.
• The flows of a solution are listed on a page of Power Apps, where this panel is not.

Switch in the settings window: Filter flows

Finding your way

Resizable flow columns

Make the columns of the flows list wider, so long flow names are no longer cut off.

How to use it

1. Open My flows (Cloud flows or Shared with me).
2. Point at the right edge of a column header, such as Name: a thin line shows. Drag it to make the column wider or narrower.
3. Double-click the line to give the column its usual width again.

Good to know

• The widths are remembered in this browser, for both tabs and every environment.
• When the columns are wider than the page, the list scrolls sideways.

Switch in the settings window: Resizable flow columns

Finding your way

Resize the raw panel

Make the panel of Show raw inputs and Show raw outputs in a flow run wider, so long JSON fits.

How to use it

1. Open a flow run in the classic designer, open an action and select Show raw inputs or Show raw outputs.
2. Drag the grip on the left edge of the panel to the left or right, the same as the edge of the Search panel.
3. Double-click the grip to go back to the designer's width. With the grip focused, the arrow keys change the width too.

Good to know

• The next panel opens at the designer's width again, unless Remember panel width is on: then it opens at the width you last dragged it to.
• The remembered width is kept in this browser profile and is not synced.

Switch in the settings window: Remember panel width

Finding your way

Collapse all cards

Alt+Shift+C (Option+Shift+C on a Mac) collapses every open card of the flow, also inside loops, conditions and scopes, as if you clicked each title.

No switch: always available in the classic designer.

Finding your way

Keep your place

When you open or close a card, the card you clicked stays where it is on the screen, instead of the view jumping.

It also keeps the place sideways, when a Condition or Switch changes the width of the flow. Near the end of a flow, where there is nothing left to scroll, the extension adds empty space below the flow until you scroll up. Scrolling, a key or another click ends it. This works in a flow run too.

Always on in the classic designer, without a switch.

Finding your way

Pan the canvas

Press the middle mouse button (the wheel) on the canvas and drag: the flow moves with the pointer, in both directions. This works while editing and in a flow run.

• The pointer shows a grabbing hand while you drag, and the browser's own autoscroll is off. It does not start in editors, fields, popups or the action search panel. A middle click without moving, for example on a link, works as before.
• With Pan with left button on, the left button does the same on an empty part of the canvas, as in the new designer. That includes the empty space inside an open Scope, loop, Condition or Switch. On a card, a button or a field it works as before.
• A pan goes on for half the window past the edge of the flow, so an action at the edge can move to the middle. Scroll back as usual; the extra room goes away by itself.

The middle button is always on in the classic designer. The left button: Pan with left button in the settings window, off by default.

Finding your way

Insert before the first action

The classic designer cannot add a step before the first action inside an Apply to each, Do until, Scope, Condition branch or Switch case. The extension adds a "+" there.

How to use it

1. Select the "+" above the first action, and then Add an action.
2. Choose an operation as usual. The new step becomes the first action; the old first action runs after it.

Good to know

• You can also drag an existing card onto the "+". It turns blue where the card may go, and red, with the reason, where it may not.
• Undo removes an added step. A moved card does not undo; drag it back instead.

Switch in the settings window: Insert before first action

Editing and saving

Quick rename, note and copy

Rename an action, edit its note or copy it in one click, instead of through the card menu.

How to use it

1. Point at a card: a pencil, a note and a copy button appear after its name.
2. Select the pencil, type the new name and press Enter. Escape keeps the old name.
3. Select the note button to add a note, or to edit the note the action already has.
4. Select the copy button to put the action on My clipboard. It shows a check for a moment. Then paste it from the + on an arrow.

Good to know

• The buttons do what Rename, Add a note and Copy to my clipboard in the card menu do.
• Renaming and copying do not expand or collapse the card. A note is shown inside the card, so the note button expands it.
• The trigger has no pencil and no copy button, and a flow run has none of the buttons, because the designer cannot rename or copy there either.
• My clipboard is the designer's own list. It is shared by the flows open in other tabs, and it is empty again after a page reload.

Switch in the settings window: Quick rename, note and copy

Editing and saving

Paste an action

Paste a copied action straight from the + on an arrow, instead of through Add an action, the My clipboard tab and a click on the action.

How to use it

1. Copy an action: the copy button after its name, Copy to my clipboard in its card menu, or Copy as JSON in the action search.
2. Point at the arrow where it should go and select the +.
3. Select Paste with the name of the action. With more than one action on My clipboard, Paste an action lists them, the last one copied at the bottom.

A short list

• My clipboard keeps the five actions copied last. A sixth copy removes the oldest, and copying an action again replaces its older copy. This also applies to the My clipboard tab of Add an action.
• Clear My clipboard at the bottom of the list empties it, also in the other tabs with a flow open. A page reload empties it too.

Good to know

• The extension takes the designer's own steps, so the result is the same as with the My clipboard tab: an action with a name that is already used gets a number, such as Compose_2, and a pasted Scope or loop brings the actions inside it.
• Undo in the designer removes the pasted action.
• The + above the first action in a loop or other block (Insert before the first action) offers Paste too.
• A copied trigger cannot be pasted as an action and is not listed.
• After a page reload, or in another browser, My clipboard is empty. An action copied with Copy as JSON in the action search is still on the system clipboard: paste it with Cmd+V (Ctrl+V) in the My clipboard tab of Add an action there.
• When the designer cannot paste the action, for example because its connections are of another kind, the My clipboard tab stays open and shows why.

Switch in the settings window: Paste an action

Editing and saving

Select several actions

Delete or move several actions at once, instead of one by one.

How to select

• On the canvas, Cmd+click (Ctrl+click on Windows) the header of a card. It gets a blue outline. Click it again the same way to take it out.
• In the Action search panel, tick the box before an action, also one inside a collapsed block. Cmd/Ctrl+click on a row does the same, Shift+click selects the rows in between, Alt+S the selected row and Alt+A every result of the search.
• The canvas and the panel share the selection. A bar at the bottom of the canvas counts it; Clear or Escape empties it.

Delete

1. Select Delete in the bar.
2. The bar asks first. It says how many actions inside the selected blocks go too, and which other actions use the ones you delete.
3. Select Delete again. Undo in the bar, or in the command bar, brings them all back at once, until you save.

Move

1. Select two or more actions.
2. Drag one of them to an arrow, into an empty branch, or to the + above the first action of a block, as you would drag one card. The other selected cards fade while you drag.
3. All selected actions go there, after each other, in the order they had in the flow. With 1 to 5 in a row and 1, 3 and 5 dragged to the arrow below 2, the flow becomes 2, 1, 3, 5, 4.

Good to know

• A block goes with everything in it. A selected action inside a selected block is not moved or deleted on its own.
• The designer's Undo does not take back a move, not even of one card. Move back in the bar puts the actions back where they were.
• If the designer refuses a place, for example above the action whose output one of them uses, nothing is moved and the bar says why.
• The trigger, a Switch case and a flow run cannot be selected.

Switch in the settings window: Select several actions

Editing and saving

Multiple conditions

A Filter array and a Do until take one condition in basic mode. More than one needs an expression in advanced mode. The extension puts the Condition action's own editor in the card, with rows and groups with And or Or, and writes that expression for you.

How to use it

1. Expand a Filter array or Do until and select Edit with multiple conditions under its condition.
2. Fill in each row as in a Condition: a value, a comparison such as is equal to or contains, and a second value. Dynamic content and Expression work as in any field.
3. + Add adds a row or a group. The … menu of a row or group has Move up, Move down, grouping and Delete.

Good to know

• Each change writes an expression such as @and(equals(item()?['Status'], 'Open'), greater(item()?['Age'], 18)) in advanced mode, so the flow works without the extension.
• A filter or loop that already has more than one condition opens with its rows. With one condition the card looks as usual; Hide multiple conditions goes back to it. Undo and edits in the expression box show in the rows.
• A value such as item() shows as an fx expression; select it to edit it.
• The card gets wider for groups inside groups. The expression box above grows with the expression; drag its lower right corner to make it higher.
• A function that is not a comparison, such as empty(item()?['Status']), is a row is equal to true, as in a Condition, and stays empty(...) in the expression.
• An expression that is not one condition, such as text with @{...}, cannot be shown as rows. Start over replaces it with one empty row. The extension never replaces it on its own.
• Edit in basic mode only works with one condition, because basic mode has one row.

Switch in the settings window: Multiple conditions

Editing and saving

Full expressions in conditions

The rules of a Condition cut each value off, such as d/File/C… or empty(…). Read every rule written out in full, without hovering each value.

How to use it

1. Expand a Condition, or a Filter array or Do until with multiple conditions.
2. Select Full expressions next to + Add.
3. Each rule gets a line under it with its first value, the operator and its second value in full. Hide full expressions removes the lines again.

Good to know

• The choice holds for every Condition, in every flow, until you change it.
• An input of a manual or Power Apps (V2) trigger, such as triggerBody()?['boolean'], shows the name it has in the trigger next to it, such as Is cancelled. The tooltip of its token shows that name too, also without the lines, and so does Condition rules in a run.
• In a flow run, the Conditions panel of Condition rules in a run has Full expressions in its header too. It is the same choice: switching it there switches it in the editor.
• The lines are only shown; the flow itself does not change.

Switch in the settings window: Full expressions in conditions

Editing and saving

JSON editor

A flow is one JSON definition, but the classic designer only shows it read-only in Peek code. The extension lets you edit it, for the whole flow or for one action, and loads the result into the designer.

How to use it

1. Select JSON in the command bar for the whole flow, or Edit JSON in the … menu of a card for that action.
2. Edit the JSON.
3. Select Apply, or press Cmd/Ctrl+Enter. The cards show the change.
4. Check the flow, and select Save yourself.

Good to know

• Apply does not save. Undo in the command bar reverts it.
• Invalid JSON is not applied: the editor names the line and column and selects the error.
• Cmd/Ctrl+F searches and replaces; Format indents the JSON again.
• A loop, scope, condition or switch includes its actions. Rename an action with Rename, not in the JSON.

Switch in the settings window: JSON editor

Editing and saving

Safe save

The designer only takes in a new value when you leave the field, and with many cards open that takes up to a second. A Save in that time can save the old value. Safe save prevents that.

What happens when you save

1. The extension takes the focus out of the field you were editing.
2. It waits until the designer has processed the change, at most 4 seconds.
3. Then it presses Save for you.

Usually that adds about 0.3 seconds.

Switch in the settings window: Safe save

Editing and saving

Faster rendering

With many cards open, the classic designer freezes for a second or more after each click in a field. The extension removes most of that wait.

• Less redrawing. After a change, the designer redraws every card of the flow. With this option, the card you work in redraws right away, and the others catch up a moment later, while you continue.
• No waiting for the popup. The designer waits 250 ms before it shows a change. After a click in a field, the extension skips that wait, so the dynamic content popup appears almost at once.

In a flow with 70 open actions, a click in a field went from 1.0–1.7 seconds to 0.3–0.6 seconds.

Switch in the settings window: Faster rendering (on by default)

Look

Themes

Give the classic designer a fresher look, closer to the new designer, without changing how it works.

• Classic: the designer as Microsoft made it. This is the default.
• Modern: cards with rounded corners and a soft shadow, on a dotted canvas.
• Minimal: flat white cards with a small rounded icon, on a plain light canvas.
• Midnight: rounded light cards on a dark dotted canvas.
• Nord: cool blue-grey canvas and cards, after the Nord palette.
• Sand: warm paper canvas with softly rounded cards.
• High contrast: white cards with dark borders, no shadow, solid black arrows and strong outlines for the selected card.
• Compact: like Modern, with lower card headers and shorter arrows between the cards, so more of a flow fits.
• Retro: square grey cards with a beveled frame on a teal canvas, like Windows 95.

Every theme other than Classic also gives arrows that are lighter (solid black in High contrast), action names in bold, and rounded fields and buttons. The selected card keeps its purple border. Below, the nine looks in turn, and then the Modern theme:

The colors of the connectors stay as they are, so you still recognize your actions at a glance.

The dynamic content and expression popup gets the same softer look. It has rounded corners, a soft shadow and no arrow, purple underlined tabs, a rounded search field, calm list items, a lightly framed expression editor and a filled purple OK or Update button, with outlined Format and One line buttons. The popup follows the theme: dark in Midnight, beveled and square in Retro. The code editor inside stays white, and Classic is unchanged.

Choose it in the extension popup, under Theme (Classic by default)

Look

Font of the action names

Choose the font and weight of the names on the cards, with or without a theme.

• Default font: the designer's own font. This is the default.
• System: the font of your computer, San Francisco on a Mac and Segoe UI on Windows.
• Inter, Roboto, Open Sans, Montserrat and Poppins: popular modern fonts, included in the extension.
• Serif: a font with serifs, such as Charter or Georgia.
• Mono: a monospace font, a little smaller.

The weight is Default weight, Regular, Semibold or Bold. The included fonts come with the extension, so nothing is downloaded from the internet.

Choose it in the extension popup, under Action names (the designer's own font by default)

Look

Smooth expand

When you open a card, its contents fade in with a small slide instead of appearing at once.

It takes 150 ms and only affects the card you open. Closing a card is instant, and the animation is off when your computer is set to reduce motion.

Turn it on or off in the extension popup, under Smooth expand in the Theme card (on by default)

Reference

Keyboard shortcuts

Change the first four on chrome://extensions/shortcuts, or via Change shortcuts in the extension popup.

Reference

Turning features on and off

Every feature has a switch in the settings window. Open it with Open all settings, or one of the groups, under Classic designer in the extension popup. The window opens in the middle of the browser window, groups the features, has a search box, a Guide button and a How it works link per feature, and stays open next to Power Automate; a change applies right away. All are on by default, except Center expression popup and Pan with left button. With a switch off, that part of the designer works exactly as Microsoft made it.

• Confirm with the keyboard, Collapse all cards, Keep your place, the handle that moves the popup and panning with the middle button have no switch and are always available.
• With the modern designer selected, the switches are grayed out. They keep their setting for when you switch back.

Check features

The extension relies on parts of the designer that Microsoft can change without notice. A feature then stops working, without an error. With a flow open in the classic designer, select Check features at the bottom of the popup. Each feature shows Works, Problem, Not checked or Off.

What's new

After an update with new features, a dialog like the tour pages through them, once, one card per feature, with a Learn more link to the matching section. It includes what changed in versions you skipped. Skip or Done closes it, also on your other computers. To see it again later, select What's new at the bottom of the popup. The changelog lists every version.

Feedback and reviews

Found a bug or have an idea? Send feedback, or select Feedback at the bottom of the popup. The form fills in the version of the extension and of your browser, and asks for your email only if you'd like a reply. If the extension helps you, a review in the Chrome Web Store helps others find it. The popup asks for one once, a week after you install or update it.