Most teams know Power Automate can save time, yet they stall at the same question: what should we actually automate first? A blank flow canvas is not very helpful when you are staring at a backlog of repetitive work. The fastest way past that block is to copy proven patterns. So this guide walks through real Power Automate examples grouped by the work they remove, from email triage and approvals to invoice processing and Power BI alerts.
Each example below names the trigger that starts the flow and the connectors it touches, so you can see how the pieces fit before you build. These are the same kinds of process automation patterns Kanerika ships for enterprise clients, scaled down to flows a single team can stand up in an afternoon. Power Automate sits inside the broader Microsoft Power Platform alongside Power Apps and Power BI . It connects to more than a thousand services, which is why the same tool shows up in finance, HR, IT, and operations. It is one of several AI automation tools teams compare when they start automating, and it overlaps with broader low-code automation platform goals.
Key Takeaways Power Automate examples fall into clear buckets: email and file management, approvals and HR, data and task routing, finance, IT operations, and reporting, so picking a starting point is a matter of finding your busiest bucket. Every flow has three parts that matter before you build: a trigger that starts it, the connectors it talks to, and the action it takes, and naming those three turns a vague idea into a buildable flow. Cloud flows handle app-to-app automation like approvals and notifications, while desktop flows (the RPA side) drive legacy apps and websites that have no API. The highest-value early wins are approvals, invoice and accounts payable handling, and onboarding, because they remove repeated manual steps that block other people from working. Power Automate scales from a single citizen-developer flow to enterprise-wide intelligent automation , but governance, error handling, and connector licensing decide whether it stays reliable at scale. Kanerika, a Microsoft Solutions Partner for Data and AI, has used Power Automate to cut manual accounts payable work by 90% and migrate teams off UiPath with a 75% drop in licensing costs. What Power Automate Does Before We Get to the Examples Power Automate, once called Microsoft Flow, is a cloud service for building automated workflows between apps without writing code. A flow watches for something to happen, then carries out a set of actions in response. The thing it watches for is the trigger, the apps it works with are connectors, and the steps it performs are actions. Understanding those three words is enough to read every example in this guide.
Case Study
UiPath to Power Automate Migration Cuts Licensing 75%
Kanerika migrated Trax from UiPath to Power Automate, cutting annual licensing costs by 75% and halving migration effort with automated accelerators, while keeping every workflow reliable.
Read the Case Study → There are two broad flow types defined by Microsoft , and they map to two different jobs. Cloud flows run in the background and connect modern apps through their APIs, which covers most of what follows here, including Power Automate connectors for Outlook, SharePoint, Teams, and Dataverse. Desktop flows, the Power Automate Desktop side, record clicks and keystrokes to drive applications that have no API at all, which is the classic RPA use case for legacy systems. Many real solutions combine both, which is how teams move from single flows toward full intelligent workflow automation .
Email and File Management Examples Email is where most people feel the drag of manual work, so it is the natural first bucket. These flows clear the small, constant tasks that interrupt focused work.
Save Email Attachments to SharePoint or OneDrive Trigger: a new email arrives in a monitored mailbox. Connectors: Outlook or Office 365, plus SharePoint or OneDrive. The flow filters for messages with attachments, then drops each file into a designated library and can log the sender and date to a list. Finance teams use this to capture invoice PDFs the moment they land, and operations teams use it to collect supplier documents without anyone touching the inbox.
VIP and High-Importance Email Alerts Trigger: a new email from a specific sender or flagged high importance. Connectors: Outlook, plus Teams or a mobile notification. Instead of watching the inbox, the recipient gets a Teams message or push alert only when something genuinely urgent arrives. This is a small flow that protects attention, which is why it spreads quickly once one person on a team builds it.
Daily Digest of New Files or List Items Trigger: a recurrence schedule, usually each morning. Connectors: SharePoint and Outlook. The flow gathers everything added to a folder or list in the last day, formats it into a single email, and sends it to stakeholders. It replaces the habit of several people separately checking the same library for updates.
Document Approval and Metadata-Based Archiving Trigger: a file uploaded to a library, or a file whose status column changes. Connectors: SharePoint, Approvals, and Outlook. When a document lands in a review library, the flow routes it through the built-in Approvals action , updates the status column to approved or rejected, and notifies the owner. A companion rule watches metadata so that anything marked archived moves to an archive library on its own. This pair keeps a SharePoint site clean without anyone running a manual cleanup, and it is a common first step toward broader intelligent document processing .
Approvals and HR Examples Approvals are the single most common thing organizations automate, and for good reason. A manual approval is a chain of emails that stalls the moment one person is out of office. Power Automate turns that chain into a tracked, auditable flow.
Time-Off and Leave Requests Trigger: a form submission, often Microsoft Forms or a SharePoint list entry. Connectors: Forms, Approvals, Outlook, and a calendar. An employee submits a request, the flow routes it to the right manager through the Approvals action, and on approval it creates a calendar hold and notifies HR. Everyone sees the status, and nothing sits forgotten in an inbox.
Kanerika Service
RPA and Power Automate Services
Kanerika designs, builds, and governs Power Automate and RPA solutions end to end, from a first approval flow to an enterprise automation practice with the controls that keep it reliable.
Explore RPA Services New Employee Onboarding Trigger: a new record in an HR system or a SharePoint onboarding list. Connectors: Dataverse or SharePoint, Teams, Outlook, and Planner. When a new hire is added, the flow provisions access requests across IT and HR, assigns welcome tasks in Planner, and spins up a Teams channel for the new starter. This is the kind of repetitive coordination that RPA and Power Automate handle far more reliably than a checklist. Kanerika built an HR onboarding automation that cut onboarding time in half while holding service-level adherence at 100%.
Contract and Certification Renewal Reminders Trigger: a scheduled recurrence that scans dates. Connectors: SharePoint or Dataverse and Outlook. The flow watches contract or certification expiry dates and emails the owner at the 120, 60, and 30-day marks. It quietly removes the risk of a renewal slipping through, which is exactly the sort of compliance automation that auditors like to see.
Finance and Invoice Examples Finance is where automation pays back fastest, because the work is high volume, rule based, and expensive when it goes wrong. These are among the strongest Power Automate examples for a return on effort, and they mirror the wins teams see with RPA in finance .
Invoice Capture and Routing Trigger: an invoice PDF arrives by email or lands in a folder. Connectors: Outlook, AI Builder or a document model, SharePoint, and Approvals. The flow reads key fields from the invoice, files the document, and routes it for approval based on amount and cost center. Pairing Power Automate with AI Builder pushes this toward true accounts payable automation rather than simple filing.
Case Study
90% Less Manual Work in Accounts Payable
A finance team buried in manual accounts payable tasks deployed Kanerika’s AP automation on Power Automate, reducing manual intervention by 90% and processing invoices 30% faster.
Read the Case Study → Accounts Payable Approval Chains Trigger: a captured invoice ready for sign-off. Connectors: Approvals, Outlook, Teams, and a finance system. The flow applies approval rules, escalates when someone does not respond, and writes the outcome back to the ledger. Kanerika deployed exactly this pattern for a finance team and reduced manual intervention by 90% while speeding invoice processing by 30%.
Expense and Purchase Request Workflows Trigger: a submitted expense or purchase form. Connectors: Forms or Power Apps, Approvals, and Outlook. Requests route by policy thresholds, with low amounts auto-approved and larger ones escalated, which keeps spend controlled without a person checking every line.
AI Builder Document Data Extraction Trigger: a PDF or scanned form arriving by email or landing in a SharePoint folder. Connectors: Outlook or SharePoint, AI Builder, and Dataverse or a list. The flow uses an AI Builder document model to read named fields from an invoice, purchase order, or receipt, writes the values to a list, and flags any low-confidence reads for a human to check. This is the step that turns simple file filing into real intelligent document processing , and it is one of the clearest places where Power Automate moves past rules into AI-assisted work. You can adapt many of these patterns from the official Power Automate connectors reference rather than building each from scratch.
Data and Task Routing Examples This bucket covers the connective tissue work, moving information between systems and turning one event into several coordinated actions.
Customer Feedback Routing Trigger: a new survey or form response. Connectors: Forms, SharePoint, Teams, and a CRM. The flow logs every submission, sends positive feedback to marketing for testimonials, and creates a service task for anything negative, so nothing slips between teams.
Watch on YouTube
RPA and Automation Use Cases in Action
See how robotic process automation and Power Automate-style workflows remove repetitive work across finance, HR, and operations.
Event and Webinar Registration Trigger: a registration form submission. Connectors: Forms, SharePoint, Outlook, and a calendar. The flow adds the registrant to an attendee list, creates the calendar event, and sends a confirmation with a calendar invite, replacing a manual copy-paste sequence.
CRM Lead Sync and Assignment Trigger: a new lead in a web form or marketing tool. Connectors: Dataverse or a CRM, Outlook, and Teams. New leads are created in the CRM, assigned to a rep by territory, and announced in a Teams channel, which shortens the gap between a lead arriving and someone owning it. This is a natural fit for broader AI workflow automation as volumes grow.
IT and Operations Examples IT teams use Power Automate to take the toil out of provisioning, monitoring, and routine maintenance, the same toil that customer service automation removes on the support side.
Access and Provisioning Requests Trigger: a request submitted to a service desk or list. Connectors: SharePoint, Approvals, Azure AD, and Teams. The flow routes the request for approval, provisions the access, and notifies the requester, with a full audit trail for security review.
Help Desk Ticket Routing and Categorization Trigger: a support request arriving by email, a form, or a Teams message. Connectors: Outlook or Forms, SharePoint or Dataverse, Teams, and a service desk such as ServiceNow or Jira. The flow reads the request, categorizes it by keyword or priority, routes it to the right support queue, logs the ticket, and sends an instant acknowledgment so the requester is not left wondering. This is one of the busiest patterns in IT, and it is a natural building block for wider enterprise workflow automation .
Listen on Spotify
Inside Enterprise Automation and the Power Platform
System and Site Monitoring Alerts Trigger: a scheduled check or an incoming webhook. Connectors: HTTP, Teams, and Outlook. The flow pings an endpoint or reads a status feed and raises a Teams alert when something is down, giving the team a head start before users complain.
Routine Database and File Cleanup Trigger: a scheduled recurrence. Connectors: SQL Server or SharePoint and Outlook. The flow archives old records, removes stale files, and reports what it did, which keeps systems tidy without a standing reminder on someone’s calendar. For high-volume, legacy-app cleanup with no API, a desktop flow handles the steps a cloud flow cannot reach, which is where process automation tools earn their place.
Reporting and Power BI Examples Reporting flows close the loop between data and the people who act on it.
Power BI Data Alerts to Teams Trigger: a Power BI data alert crossing a threshold. Connectors: Power BI, Teams, and Outlook. When a metric breaches a limit, the flow posts to the right Teams channel so the owner reacts in minutes, not at the next review. This is one reason teams weigh Power Automate against Power BI as complementary rather than competing tools.
Scheduled Report Distribution Trigger: a recurrence schedule. Connectors: Power BI, SharePoint, and Outlook. The flow exports a report to PDF and emails it to a distribution list on a fixed cadence, removing the Monday-morning export-and-send ritual.
Planner Task Completion Alerts Trigger: a task marked complete in Microsoft Planner. Connectors: Planner, Teams, and Outlook. The flow posts an update to the relevant Teams channel or messages the project lead the moment a task closes, so progress stays visible without anyone opening the Planner tab to check. It removes the steady drip of status-chasing messages that slow project work, and it is the kind of small flow that proves the value of automation to a skeptical team fast.
Meeting Action and Notes Tracking Trigger: a Teams meeting ending or a notes entry. Connectors: Teams, Planner, and Outlook. The flow captures action items, converts notes to a shared format, and assigns follow-ups, so decisions do not evaporate after the call.
Cloud Flows vs Desktop Flows: Which Example Belongs Where A recurring question once teams start building is whether a given example should be a cloud flow or a desktop flow. The short answer: if the apps involved have APIs, use a cloud flow; if you have to drive a screen a human would click, use a desktop flow. The table below maps the two against the work they suit.
Dimension Cloud Flows Desktop Flows (RPA) Best for Modern apps with APIs: Outlook, SharePoint, Teams, Dataverse, Power BI Legacy apps, desktop software, and websites with no API How it works Calls connectors in the background, triggered by events or schedules Records and replays clicks, keystrokes, and screen reads Runs In the cloud, unattended, always on On a machine, attended or unattended via a gateway Typical examples Approvals, email alerts, invoice routing, Power BI alerts Data entry into old ERPs, screen scraping, bulk legacy updates Skill needed Citizen developer, low-code Low-code recorder, but needs care on UI changes
How to Turn an Example Into a Reliable Flow Copying an example gets a flow running. Keeping it running at scale takes a few more habits. Name the trigger, connectors, and actions before you build, so the flow has a clear shape. Add error handling with configure-run-after settings so a single failed step does not silently stop the whole flow. Use environment variables and connection references rather than hard-coded values, which makes a flow portable between test and production. And watch connector licensing early, because premium connectors like Dataverse and many third-party services sit outside the standard Microsoft 365 plan.
Governance is the difference between ten useful flows and a hundred unmanaged ones. As adoption grows, a center of excellence, naming standards, and monitoring keep things from sprawling, which is the same discipline that separates hobby automation from enterprise automation . Teams that outgrow simple flows often graduate toward agentic automation , where AI agents handle decisions the rules could not, blurring the old line between artificial intelligence and automation . When the choice is between platforms, our take on UiPath versus Power Automate and Zapier versus Power Automate can help you decide.
Power Automate vs Logic Apps vs Zapier: Picking the Right Tool Power Automate is not the only way to wire apps together, and the right choice depends on who builds the flow and where the work lives. Zapier is the friendliest for a non-technical user stitching together popular SaaS apps. Azure Logic Apps is the developer-grade sibling of Power Automate, built for engineers who want source control and heavier integration. Power Automate sits in the middle, close to Microsoft 365 and reachable by business users who are not coders. The table below lines up the three so you can match the tool to the team.
Consideration Power Automate Azure Logic Apps Zapier Built for Business users inside Microsoft 365 Developers building enterprise integrations Non-technical users connecting SaaS apps Ecosystem fit Deep with Outlook, SharePoint, Teams, Dataverse Deep with Azure services and APIs Broad with consumer and SaaS apps Desktop RPA Yes, through desktop flows No native desktop automation No native desktop automation Pricing model Bundled with many Microsoft 365 plans, premium add-ons Consumption based, pay per action Tiered by tasks per month Best when Your work and data already live in Microsoft 365 You need code-grade control and Azure scale You want fast setup across many outside apps
Why Teams Bring in Kanerika for Power Automate Most Power Automate examples are easy to start and hard to scale. The first ten flows feel effortless, then governance, error handling, premium-connector cost, and the limits of citizen development start to bite. That is the point where teams bring in a partner who has built automation at enterprise scale.
Talk to Kanerika
Ready to Move Past Your First Ten Flows?
Kanerika scopes which examples are worth automating, builds the cloud and desktop flows, and puts the governance in place to keep them reliable. A short working session turns your backlog into a plan.
Schedule a Demo → Kanerika is a Microsoft Solutions Partner for Data and AI that designs, builds, and governs Power Automate solutions end to end, from a first approval flow to a full RPA practice . We pair cloud and desktop flows, add AI Builder where documents need reading, and put the governance in place that keeps automation reliable. For teams on another platform, our UiPath to Power Automate migration service moves you across with the licensing savings intact, and our broader agentic AI work takes automation past static rules. The results are concrete: 90% less manual accounts payable work for one finance team, a 75% cut in licensing costs for a team leaving UiPath, and 38% faster pricing insights for a business using Power Automate analytics.
Frequently Asked Questions What are the most common Power Automate examples? The most common Power Automate examples are approval workflows, email and file automation, and invoice handling. Teams start by automating leave and purchase approvals, saving email attachments to SharePoint, alerting on important messages, and routing invoices for sign-off. These show up first because they remove repetitive manual steps that block other people from working, and because they need only standard connectors most organizations already own.
What can Power Automate be used for? Power Automate can be used to connect apps and automate repetitive work without writing code. It handles approvals, notifications, data movement between systems, scheduled reports, document processing, and form-driven workflows across Microsoft 365 and more than a thousand other services. With desktop flows it also drives legacy applications that have no API, which extends it into traditional robotic process automation territory for older systems.
What is the difference between a cloud flow and a desktop flow? A cloud flow connects modern apps through their APIs and runs in the background, triggered by events or schedules, which suits approvals, alerts, and invoice routing. A desktop flow records clicks and keystrokes to drive applications and websites that have no API, which is the classic RPA pattern for legacy systems. Many real solutions combine both, using a cloud flow to orchestrate and a desktop flow to reach an old screen.
Is Power Automate easy to learn? Power Automate is designed as a low-code tool, so building a first flow from a template takes most people an afternoon. The basics of triggers, connectors, and actions are quick to grasp. The harder parts come later: error handling, expressions, premium connector licensing, and governance at scale. Copying proven examples shortens the early learning curve significantly, because you adapt a working pattern instead of starting from a blank canvas.
How long does it take to learn Power Automate? Most people build a useful flow within a day and feel comfortable with everyday automations in two to four weeks of regular use. Reaching the level where you handle complex expressions, robust error handling, and enterprise governance takes a few months of hands-on work. The fastest path is to start with concrete Power Automate examples, ship a few real flows, and add depth as your needs grow rather than studying every feature first.
Does Power Automate cost extra beyond Microsoft 365? Many Power Automate examples run on the standard connectors included with Microsoft 365, so they cost nothing extra. Premium connectors, including Dataverse, many third-party services, and AI Builder, sit outside that plan and need a per-user or per-flow Power Automate license. The practical advice is to check connector licensing early when you design a flow, because a single premium connector can change the cost of an otherwise free automation.
What is the best way to start with Power Automate? The best way to start is to pick your busiest manual process, find a matching template or example, and build that one flow end to end. Approvals, invoice routing, and onboarding are strong first projects because they remove visible bottlenecks. Name the trigger, connectors, and action before you build, add basic error handling, and only then expand. Starting narrow and proving value beats trying to automate everything at once.
Can Power Automate replace UiPath and other RPA tools? Power Automate can replace many UiPath workloads, especially where work lives inside the Microsoft ecosystem, and teams often move to cut licensing costs and simplify maintenance. Its cloud flows cover app-to-app automation and its desktop flows cover screen-driven RPA. Kanerika migrated one client from UiPath to Power Automate and cut annual licensing costs by 75%. Whether it fits depends on workload complexity, existing investments, and the level of governance you need.
