5 Power Automate Flows Every SharePoint Admin Should Build
Practical, immediately usable automation workflows that reduce manual work and improve document governance — with step-by-step setup notes.
Power Automate and SharePoint together form one of the most underutilised combinations in Microsoft 365. Organisations pay for Power Automate as part of their M365 licence but leave it untouched while staff manually chase approvals by email, forget to review expiring contracts, and spend hours on onboarding tasks that could be automated in an afternoon. These five flows fix the most common manual bottlenecks in SharePoint-heavy environments.
Before You Start: Power Automate Basics for SharePoint
-
1Create a new cloud flow
Go to powerautomate.microsoft.com > Create > Automated cloud flow > select a trigger (SharePoint trigger like 'When an item is created' or 'When an item is modified'). Name your flow.
-
2Configure your SharePoint trigger
Select your SharePoint site and list. Set any filtering conditions (e.g., 'Only trigger for items where Status = Pending'). Configure trigger frequency if needed. Click Create.
-
3Add actions to process the item
Add actions like 'Get file properties', 'Update item', 'Send email', 'Create event in calendar', or 'Post to Teams'. Each action pulls data from the trigger using dynamic content tokens like @{triggerOutputs()['body/ID']}.
-
4Configure conditional logic (if needed)
Add 'Condition' actions to branch logic: if Status = Approved, send approval email; if Status = Rejected, move item to archive. Use comparison operators (is equal to, contains, greater than).
-
5Add error handling
Add 'Configure run after' to the final action to catch failures. Set it to run if the previous action 'has failed' or 'has timed out'. Log errors to a Teams channel or email for visibility.
-
6Test and monitor
Save and test the flow by manually creating a SharePoint item. Monitor the flow run history in Power Automate to confirm all steps executed. Adjust actions and conditions based on real results.
Power Automate flows have three parts: a trigger (what starts the flow), conditions (optional logic), and actions (what happens). SharePoint triggers include "When an item is created," "When a file is created," "When a file is modified," and a recurrence trigger for scheduled flows.
All five flows below require a Microsoft 365 business licence that includes Power Automate (Business Basic, Standard, Premium, or any Enterprise plan). Build and test in the Power Automate maker portal at make.powerautomate.com. Always test with a sample item before turning on flows that send emails or modify data.
Flow 1: Document Approval Workflow
Flow 01
New document submitted → manager approves → file moves to Approved folder
The most common SharePoint workflow request. Without automation, approval requests get lost in email threads. This flow creates a structured, auditable approval chain.
- Trigger: When a file is created in a SharePoint library (e.g., "Pending Approval" folder)
- Action: Start and wait for an approval — send to the document's author's manager (use Office 365 Users connector to look up manager automatically)
- Condition (Approved): Move file to "Approved" library folder; update a Status column to "Approved"; notify the submitter via Teams or email
- Condition (Rejected): Move file back to "Drafts" folder; send rejection reason to submitter; log outcome in a SharePoint list for audit trail
Pro tip: Add a 3-day timeout on the approval action. If no response is received, send a reminder email and re-request. If still no response after 5 days, auto-escalate to the manager's manager.
Flow 2: Contract & Document Expiry Reminders
Flow 02
Date column approaches expiry → alerts sent to document owner at 90, 30, and 7 days
Contracts, certifications, licences, and policies all have expiry dates. Without reminders, they expire unnoticed. This recurrence-triggered flow runs daily and catches expiries before they become problems.
- Trigger: Recurrence — run daily at 8 AM
- Action: Get items from SharePoint list where "Expiry Date" is within the next 90 days and "Status" is not "Expired"
- Loop: For each item, calculate days remaining using the DateDiff expression
- Condition: If days remaining = 90, 30, or 7 — send an email to the "Owner" column value with a direct link to the document and expiry date
- Action (Day 0): Update "Status" column to "Expired" and send final alert with escalation copy to line manager
Flow 3: New Employee Onboarding Automation
Flow 03
HR creates new hire record → SharePoint site provisioned, welcome email sent, Teams channel created
Manual onboarding can take HR and IT several hours per new employee. This flow reduces the repeated coordination work and gives every team the same checklist, timing, and audit trail.
- Trigger: When a new item is created in the HR "New Employees" SharePoint list
- Action: Send a welcome email to the new hire's personal email (pre-start) with first day information and a link to the onboarding portal
- Action: Create a private Teams channel in the department team named "Onboarding-[FirstName]" and add the new hire, their manager, and an HR rep
- Action: Post an onboarding checklist as a message in the new channel — including IT setup tasks, policy acknowledgement links, and first-week meeting schedule
- Action: Create Planner tasks assigned to IT with hardware provisioning steps and a due date of the start date minus 2 days
Pro tip: Add a parallel branch that sends notifications to IT, payroll, and facilities simultaneously — each with only the fields relevant to their role — rather than one long email to everyone. For an in-depth look at the site provisioning step, including self-service intake forms and approval gates, see our SharePoint site provisioning automation guide.
Flow 4: Stale Content Governance Alert
Flow 04
Files unmodified for 180+ days → owner alerted to review, archive, or delete
Stale content is the enemy of SharePoint search quality and governance. This flow surfaces neglected documents before they become compliance risks.
- Trigger: Recurrence — run monthly on the 1st
- Action: Get files from target library where "Modified" date is more than 180 days ago and "Reviewed" column is empty or older than 180 days
- Loop: For each item, retrieve the "Author" or site owner from SharePoint metadata
- Action: Send a digest email to each owner listing their stale files with direct links. Include three action buttons: "Still needed," "Archive this," "Delete this" — each triggering a follow-up flow action via Power Automate HTTP triggers
Flow 5: Multi-Level Approval with Escalation
Flow 05
Request submitted → L1 approval with timeout → auto-escalate to L2 → final decision logged
For high-value decisions — budget requests, policy exceptions, vendor contracts — single-approver flows aren't sufficient. This pattern enforces accountability with automatic escalation.
- Trigger: When an item is created in a "Requests" SharePoint list with "Approval Required" = Yes
- Action: Start approval — send to L1 approver (e.g., direct manager). Set a 48-hour timeout
- Condition (timeout reached, not approved): Send reminder to L1. Start a second 48-hour wait. If still no response, send to L2 (skip-level manager) with "Escalated due to non-response" context
- Condition (approved at any level): Update "Status" to Approved, log approver name and timestamp to the SharePoint item, notify submitter
- Condition (rejected): Update "Status" to Rejected, log rejection reason, notify submitter with reason and guidance on resubmission
Pro Tips for All Five Flows
- Use variables for repeated values. Set your document library name, approver email, and notification prefix as variables at the start of the flow — not hardcoded in each action. Changing a library name means updating one variable, not hunting through 12 actions.
- Always test with a sample item first. Use the "Test" button in Power Automate with a manual trigger before enabling. Run through both the approval and rejection paths.
- Add error handling. Use a "Run after" condition on critical actions so the flow sends an alert to an admin if an action fails instead of silently stopping.
- Document your flows. Add a description to every flow and note the SharePoint site, list, and columns it depends on. Undocumented flows become unmaintainable when the person who built them leaves.
- Review run history monthly. Power Automate's run history shows every execution. A flow with repeated failures needs investigation — not just occasional spot checks.
Need Power Automate flows built for your SharePoint environment?
We design and build production-ready Power Automate workflows scoped to your specific processes — with error handling, testing, documentation, and knowledge transfer included. Start with a free 60-minute consultation.
Book a Free Consultation →Frequently Asked Questions
The five highest-value flows are: document approval with email and Teams notifications, contract expiry reminders triggered by a date column, new employee onboarding triggered from an HR list, stale content alerts for libraries not updated in 90+ days, and multi-level escalation approvals for sensitive documents.
Yes.
The SharePoint connector includes 'Get items', 'Get item', 'Create item', 'Update item', and 'Delete item' actions. You can filter items using OData queries, update specific fields, and work with attachments — all without writing any code.
Use the 'When a file is created (properties only)' trigger on your document library.
This fires for new uploads and provides the file metadata. For files created in subfolders, enable the 'Include subfolders' option in the trigger settings.
Common causes: the flow is turned off, the trigger is on the wrong site or library, the triggering user is the flow owner (owner-triggered flows can sometimes self-suppress), or throttling from high list activity.
Check the flow's run history in Power Automate for the exact error. Also verify the flow has permission to access the SharePoint site.
Editing and saving a flow creates a new version. Approvals that started on the old version continue running on that version until they complete or time out.
New triggers use the new version. Avoid editing flows with many in-flight approvals — instead, build a v2 flow and turn off the old one after in-flight runs complete.