A purchase approval flow in Power Automate, step by step
In many companies a purchase request still lives in an e-mail thread. Someone asks, the manager doesn’t answer, and a week later nobody knows where it is. If you already pay for Microsoft 365, you can fix this with Power Automate and no extra software: the request goes into a list, the approval lands in the manager’s Teams or Outlook, large amounts go to a second approver, and every decision is recorded next to the request.
This guide builds that flow from start to finish.
Before you start
- Licence: Approvals, SharePoint, Outlook and Teams are standard connectors, so a Microsoft 365 licence that includes Power Automate is enough (Microsoft Learn).
- Storage: Approvals are stored in Microsoft Dataverse. In the default environment the database is created for you the first time an approval flow runs.
- Managers: If you want the flow to find each requester’s manager on its own, managers need to be set in Microsoft Entra ID.
1. The request list
Create a SharePoint list. These columns are a good start:
| Column | Type | Purpose |
|---|---|---|
| Title | Single line of text | What to buy |
| Amount | Number | Net amount |
| Reason | Multiple lines of text | Why it’s needed |
| Status | Choice | Pending, Approved, Rejected |
| ApprovedBy | Single line of text | Who made the final call |
| DecisionNote | Multiple lines of text | The approver’s comment |
You don’t need a “requested by” column: SharePoint keeps Created By for every item.
One detail that saves trouble later: SharePoint derives a column’s internal name from the first name you give it, and encodes spaces and special characters (a space becomes _x0020_). Expressions in your flow use the internal name, so create columns without spaces or accented characters first and rename them afterwards (SharePoint naming guidelines). This matters even more if your team names columns in Turkish.
2. Create the flow
- In Power Automate, go to My flows → New flow → Automated cloud flow.
- Pick the SharePoint trigger When an item is created.
- Select the site and the list.
Avoid “When an item is created or modified” here. The reason is in the common mistakes below.
3. First approval: the line manager
Add Start and wait for an approval from the Approvals connector.
- Approval type: Approve/Reject - First to respond for a single approver.
- Title: “Purchase request: ” followed by the item title.
- Assigned to: the approver’s e-mail. To route to the requester’s manager automatically, add Get manager (V2) from Office 365 Users first and use its e-mail. If no manager is set in Entra ID, that action fails with “No manager found”.
- Details: the amount and the reason. Markdown works here.
The approver can respond from the e-mail in Outlook, from the Approvals app in Teams, or from the approvals centre in Power Automate (approvals in Teams). The flow waits at this step until a decision comes in.
4. Check the decision
Add a Condition that compares the approval’s Outcome with Approve. The value is case-sensitive: approve never matches.
- The False branch is a rejection: update the item and notify the requester (steps 6 and 7).
- The True branch continues.
5. A second approval above a threshold
The sample model on this site uses a simple rule: requests over 50,000 TL also go to the finance director after the manager. Use whatever threshold and currency fit your company.
- In the True branch, add a Condition: Amount is greater than
50000. - In its True branch, add a second Start and wait for an approval assigned to finance.
- Check its outcome the same way as in step 4.
To avoid repeating the final steps in every branch, keep the result in a variable: Initialize variable at the top, Set variable after each decision, then update the item and send the e-mail once at the end.
If every request needs both approvals, skip the condition and choose the Sequential approval type instead. The request only moves to the next approver after the previous one responds.
6. Record the decision
Use SharePoint’s Update item:
- Id and Title from the trigger (Site Address, List Name, Id and Title are required).
- Status: Approved or Rejected.
- ApprovedBy: the approval’s Responses Approver name.
- DecisionNote: Responses Comments.
Now every request carries who decided and why. When someone asks “who approved this purchase?”, the answer is in the list.
7. Tell the requester
Send the result with Office 365 Outlook’s Send an email (V2), addressed to Created By Email from the trigger. If you include the decision time, note that approval timestamps are always in UTC (known limitations); use Convert time zone to show local time.
If an approval can take more than 30 days
A cloud flow run can last at most 30 days, including steps waiting for approvals. After 30 days, pending steps time out (flow limits).
Purchase approvals rarely take that long. If yours might, Microsoft’s recommended pattern is two flows: one sends the request with Create an approval (v2), the other runs your business logic when the response arrives. Because approvals live in Dataverse, the response isn’t lost when the first run ends (long-running approvals).
Common mistakes
Using “When an item is created or modified”. That trigger fires on every change. When your flow updates the same item in step 6, that’s a change too, and the flow starts again. Use When an item is created for new requests, and add trigger conditions if you really need to react to edits (trigger conditions).
Pinning approvals to one person. Requests stall when they’re on leave. Put several addresses in Assigned to (separated by semicolons) with First to respond, or assign the approval to a Microsoft 365 group.
A single flow owner. If the creator leaves and the flow still has another active owner, it keeps running, but steps using connections that belonged to the person who left may fail. Add a co-owner and know whose account each connection uses (sharing flows).
Forgetting whose name appears. The flow creator’s name is always shown in approval details, to prevent spoofing. Building the flow with an account approvers recognise avoids confusion.
Letting a rarely used flow lapse. A flow that isn’t triggered for 90 days may be turned off. Owners get an e-mail 30 days before, and turning it back on is enough. Flows owned by users with premium licences are exempt.
Connecting it to an ERP
Turning an approved request into an order in the ERP is the usual next step, and it changes the licensing. HTTP, SQL Server and custom connectors are premium, and so is the on-premises data gateway you need to reach a server inside your network (licence types). Budget for that before you plan the integration.
Try it first
You can run this flow as a small interactive model on this site: you open the request and you make the manager and finance decisions. See the purchase approval model. The data is sample data.
Thinking about something similar?
Approval flows, Microsoft 365 and Power Automate automation, ERP and e-invoice integrations, and company websites for small businesses.