Skip to content
Tutorials Center
My learning

Topics

Lesson 21 of 38 ยท Approvals and Control Flow

Approvals: Asking People to Decide

Add human decisions to a flow with the Approvals connector: approval types, assigning approvers, reading the outcome and responses, reminders, and what happens on timeout.

Many business processes need a person to say yes or no: a manager approves an expense, a lead signs off on a document, a customer service agent confirms a refund. Power Automate has a built-in answer for this, the Approvals connector. A flow sends a request to one or more people, pauses while it waits, and continues with their decision. Nobody has to poll a mailbox or copy answers into a spreadsheet.

This lesson explains the approval types, the fields of the action, how to read the result, and how to design the wait so it does not hang forever. The product itself cannot run on this site, so the menus are described in words and the runnable examples are labelled stand-ins that model how responses are combined.

Names of actions and options change over time. This lesson uses the labels at the time of writing; if your screen differs slightly, look for the same idea under a similar name.

What an approval is

An approval is a record stored in Dataverse (the Approvals service) that has a title, details, one or more assigned people, and a state. People answer it in several places: the notification email (actionable buttons in Outlook), the Approvals page in Power Automate, the Microsoft Teams Approvals app, and the Power Automate mobile app. The flow does not care where the answer came from.

flowchart LR
    T["Trigger<br/>new expense"] --> A["Start and wait<br/>for an approval"]
    A -->|"approver answers"| C{"Outcome"}
    C -->|"Approve"| Y["Pay and notify"]
    C -->|"Reject"| N["Notify requester"]

The flow pauses at the approval action. It resumes only when the approval is answered or the wait ends.

The two ways to use the connector

Action Behavior
Start and wait for an approval One action: creates the approval, waits, returns the result. The usual choice.
Create an approval + Wait for an approval Two actions. The gap between them lets you do other work (send a reminder, post a message, run a parallel branch) while the approval is pending.

With the two-action form, Create an approval returns immediately with an approval ID. Wait for an approval then takes that ID. Between them you can, for example, post the approval link into a chat channel.

Approval types

You pick the type when you add the action:

  • Approve/Reject - First to respond: several people are assigned, and the first answer decides. Good for a shared mailbox of approvers where anyone may handle it.
  • Approve/Reject - Everyone must approve: all assigned people answer. The overall outcome is Approve only if everyone approves; one Reject makes it Reject. Good for compliance sign-off.
  • Custom Responses - Wait for one response: you define your own buttons (for example Ship, Hold, Cancel). The first answer decides.
  • Custom Responses - Wait for all responses: you define the buttons and every person answers. The flow then decides what to do with the set of answers.

Fields of the action

Field Meaning
Title The subject shown in the email and the Approvals page. Put the key fact in it ("Expense 118.40 USD from Maya").
Assigned to One or more email addresses, separated by semicolons. Can be dynamic content such as the manager from a user lookup.
Details The body. Supports Markdown, so you can show a table or bold text.
Item link and Item link description A button that opens the record under review (a SharePoint item, a PDF, a ticket).
Requestor Who asked; shown to approvers and used for replies.
Enable notifications Sends the email and push notification. Turn it off only if people will find the request another way.
Enable reassignment Lets an approver forward the request to someone else.

A good Details field gives the approver everything needed to decide without opening anything else. A weak one just says "please approve" and sends them hunting.

Reading the result

After the wait, the action exposes dynamic content:

  • Outcome: the final answer as text. For Approve/Reject types it is Approve or Reject; for custom responses it is the text of the chosen response (or a combined value, depending on the type).
  • Responses: an array with one entry per person who answered. Each entry has the responder (name and email), the response text, the comments they typed, and the time.
  • Response summary: a ready-made text summary you can paste into an email.

The standard next step is a Condition (see conditions and switch) that checks whether Outcome equals Approve. Comments matter: when someone rejects, the comment is usually the reason you want to send back to the requester, so include it in your notification.

In expression form, a typical test looks like this (the action name has underscores in place of spaces):

TEXT
@equals(body('Start_and_wait_for_an_approval')?['outcome'], 'Approve')

How "Everyone must approve" combines answers

The type name hides a small algorithm. Try it in this stand-in, which mimics only the combining rule, not the real service.

JS Stand-in: combine approval responses

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Sequential approvals

The connector has no "chain" type. To require a manager first and then finance, add two approval actions one after the other, each inside the Approve branch of the previous Condition. The nesting grows quickly; for long chains, store the chain in a data source (a list of approver emails with an order number) and loop over it, as the loops lesson shows.

Timeouts and reminders

An approval that nobody answers keeps the flow run waiting. A cloud flow run can last at most 30 days, and an approval wait belongs to that clock, so a request left unanswered eventually fails the run with a timeout. You should decide the behavior yourself instead of waiting for that. Open the action's Settings and set a Timeout (an ISO 8601 duration such as P3D for three days). Then use the pattern from error handling with run after to branch when the action times out: remind the approver, escalate to a backup, or close the request.

JS Stand-in: escalation after a timeout

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Common mistakes

  • Approving through a shared account. Responses record who answered. Use real people or a mail-enabled group with "first to respond".
  • Hard-coded approver emails. People change jobs. Look the manager up (Office 365 Users connector) or read approvers from a list.
  • No reject path. The flow ends silently and the requester never learns the outcome.
  • Vague Details. Include amount, requester, purpose and a link.
  • Forgetting the timeout. A forgotten approval holds a run open for weeks.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which approval type decides as soon as any one assigned person answers?

    First to respond closes the approval with the first answer. Everyone must approve waits for all of them.
  2. 2. With 'Everyone must approve', two people approve and one rejects. What is the outcome?

    The combined outcome is Approve only when every responder approves.
  3. 3. Why use the two-action form (Create an approval + Wait for an approval)?

    The ID returned by Create an approval lets you act between creating and waiting.
  4. 4. What should you set so an unanswered approval does not hold a run open for weeks?

    Set an explicit timeout and decide what happens next: remind, escalate or close.

Summary

  • The Approvals connector pauses a flow until people answer, and returns an outcome, responses and comments.
  • Choose First to respond, Everyone must approve, or custom responses to match your process.
  • Give approvers complete Details and a link to the item.
  • Read Outcome in a Condition and send rejection comments back to the requester.
  • Set a timeout and handle it; chain approvals by nesting or by looping over an approver list.

Next: Conditions and Switch