This article gives you seven practical Power Automate flows you can build today, along with the permissions, licences and troubleshooting know-how to keep them running smoothly. We cover email attachments, approvals, Forms data, weekly reporting and lead capture, plus the setup steps and quick fixes for when a flow stops behaving.
TL;DR:
- Most flows rely on standard connectors like Outlook, SharePoint, and Teams, but premium features require appropriate licenses and careful connection ownership management.
- Building flows for saving email attachments, approval routing, or lead capture can be done quickly, but thorough testing and clear documentation are essential for long-term maintenance.
- Troubleshooting involves monitoring run history, setting error handling scopes, and managing connection expiry or permission issues to prevent silent failures.
- Licensing limits Action capacity at around 250,000 actions per day per Process license, which small teams can usually stay within by batching or redesigning flows.
- Enhancing flows with AI, conditional approvals, or dashboard outputs can boost productivity once the basics are stable and well-maintained.
Table of Contents
- Before you start: permissions, connectors and quick checks
- 1. Seven practical flow ideas worth building first
- Troubleshooting flows when they stop working
- Licensing and action limits that shape your design
- Keeping flows maintainable as you add more
- Creative uses beyond the basics
- Security and compliance considerations
- Connecting flows to third-party services and APIs
- Sharing and collaborating on flows with your team
- What we’ve learnt building these for small businesses
- Where TTOY Digital fits if you’d rather hand this off
- FAQ
- Sources
Before you start: permissions, connectors and quick checks
Most of the flows below lean on a small set of connectors: Outlook, SharePoint, OneDrive, Teams and Forms. A handful of more advanced ideas touch Dataverse or AI Builder, which sit behind premium licensing, so it’s worth knowing which bucket you’re in before you start dragging boxes around the canvas.
Before building anything, run through this:
- Confirm who owns each connection (your own account or a shared service account), since ownership affects what happens when someone leaves the business.
- Check token expiry on connections that use OAuth, as passwords changes and revoked consent are a common cause of silent flow failures.
- Note which connectors are marked “Premium” in the maker portal, because these need a Premium user licence or Process licence to run reliably.
- If a flow needs AI Builder credits or robotic process automation, flag it early. These usually mean a licensing conversation before build.
1. Seven practical flow ideas worth building first
These seven cover the bulk of what small teams actually need automated: paperwork, approvals, reporting and lead handling. Each one is buildable in an afternoon by someone who has never opened Power Automate before.
1. Save email attachments to SharePoint automatically
What it does: Watches a shared mailbox and saves any attachments straight into a SharePoint document library, tagging them with sender and date.
When to use it: Invoices, supplier documents or signed contracts that currently get forwarded manually and then forgotten.
Connectors needed: Outlook, SharePoint.
Setup steps: Trigger on “When a new email arrives”, loop through the attachments array with “Apply to each”, and create a file in SharePoint for each one using the attachment’s name and content. Add metadata columns (sender, subject, received date) so the library stays searchable.
Pitfall: Attachments come through as an array even when there’s only one file, so always use the loop rather than trying to grab “the” attachment directly.
2. Build a simple approval flow for leave or expenses
What it does: Routes a request through one or more approvers and notifies the requester of the outcome.
When to use it: Holiday requests, expense claims or purchase sign-off where email chains currently cause delays.
Connectors needed: Approvals, plus Teams or Outlook for notifications.
Setup steps: Use the “Start and wait for an approval” action, set the approval type to “Approve/Reject - First to respond” for single-stage requests, or chain two approval actions for multi-stage sign-off (manager then finance, for example).
Pitfall: Multi-stage approvals need clear logic for what happens on a rejection partway through, so build the “no” branch before you test the “yes” one.
3. Store Forms attachments as clickable links in SharePoint
What it does: Pulls file uploads from a Microsoft Forms submission and saves them to SharePoint, with working links written directly into a list item.
When to use it: Job applications, supplier onboarding or any form that collects documents rather than just text answers.
Connectors needed: Forms, SharePoint.
Setup steps: For each attachment, create the file in SharePoint, then append an HTML anchor tag containing the new file’s link to a string variable. Write that string into a SharePoint column set to “Enhanced rich text” so the link renders as clickable rather than as raw text, a pattern confirmed in Microsoft’s own guidance on saving Forms attachments.
Pitfall: A plain text column will show the HTML tags as text instead of a link. The column type matters more than the flow logic here.
4. Send a weekly digest instead of constant pings
What it does: Collects new items from the week (new leads, completed tasks, flagged items) and sends one summary instead of dozens of individual alerts.
When to use it: Any process generating enough notifications that people start ignoring them.
Connectors needed: SharePoint or Dataverse for the source data, Teams or Outlook for the summary.
Setup steps: Use a recurrence trigger set to weekly, pull items filtered by date with “Get items”, and use “Apply to each” to build an HTML table or bullet list in a variable before sending it as a single message.
Pitfall: Watch action limits when looping through large lists each week. Filter at the source rather than pulling everything and discarding it inside the flow.
5. Capture leads and push them into your CRM
What it does: Takes a new Forms or SharePoint entry and creates a matching record in your CRM, with a notification to the sales inbox.
When to use it: Website contact forms, event sign-ups or anywhere new enquiries currently get typed in by hand.
Connectors needed: Forms or SharePoint as the trigger, HTTP or a webhook into your CRM (including SmartFlowCRM).
Setup steps: Map form fields to CRM fields directly in the “Create record” or HTTP action, and add a lookup step beforehand to check for an existing record by email address.
Pitfall: Without a deduplication check, the same enquirer submitting twice creates two records. A simple “Get items” filter on email address before the create step solves this.
6. Email files from a SharePoint folder as attachments
What it does: Grabs one or more files from a SharePoint library and sends them out as genuine email attachments rather than links.
When to use it: Sending brochures, price lists or signed documents that need to arrive as a file, not a hyperlink.
Connectors needed: SharePoint, Outlook.
Setup steps: Build an array where each item has a “Name” and “ContentBytes” property, using “Get file content” for each file, then switch the “Send an email (V2)” attachments field to “Switch to input entire array” rather than adding files one by one, as described in Microsoft’s guidance on sending SharePoint files as attachments.
Pitfall: Forgetting to switch to array mode means the action only accepts a single file, so multi-file sends silently fail or only grab the first item.
7. Automate new starter checklists
What it does: Creates onboarding tasks, assigns owners, and chases reminders until each step is marked done.
When to use it: Any onboarding process with more than three or four repeatable steps.
Connectors needed: SharePoint or Planner, Teams for reminders.
Setup steps: Trigger on a new starter record, create a set of tasks with assigned owners, then use a scheduled recurrence to check completion status and send reminders for anything still open after a set number of days.
Pitfall: Onboarding can run longer than a single flow run comfortably allows. For anything stretching past a few weeks, save progress to a list and trigger a fresh run for the next phase rather than keeping one instance open indefinitely.
Pro Tip: Build the simplest version of each flow first, test it with real (not dummy) data, and only add branching logic once the happy path works reliably.
Troubleshooting flows when they stop working
Flows fail quietly if you let them. The fix is to build in visibility from day one rather than discovering a broken process three weeks later.
- Wrap risky actions in a Try scope, then add a Catch scope with “Configure run after” set to trigger only when the first scope fails, a pattern Microsoft’s error handling guidance recommends for keeping failures contained and logged.
- Log errors to a SharePoint list rather than firing off an email every time, so you get an audit trail instead of a flooded inbox.
- Use exponential retry policies on HTTP or API actions that talk to external services, since a brief outage shouldn’t need a human to notice and resubmit.
- Check the run history view for failed runs. Microsoft’s own flow troubleshooting guide notes that repair tips are sent to flow owners for certain failure types, and Copilot can summarise errors in plain language to speed up diagnosis.
Common culprits: a 401 or 403 usually means an expired or revoked connection, a 404 means something the flow expected (a file, a list item) has moved or been deleted, and a 500 or 502 is usually the other service having a bad moment, which is exactly when a retry policy earns its keep.
Licensing and action limits that shape your design
Power Automate licensing splits roughly into two things: what you’re allowed to use, and how much you’re allowed to run.
- A Premium user licence unlocks premium connectors, desktop flows and AI Builder features that a standard licence won’t touch.
- A Process licence, sometimes called Hosted Process, provides daily action capacity, 250,000 actions per day per licence, and these can be stacked (up to 10) or shared across a flow group covering up to 25 flows.
- For most small teams, a handful of the flows above will sit comfortably within a single Process licence’s daily allowance. It’s usually cheaper to redesign a chatty flow to batch its actions than to buy more capacity outright.
Keeping flows maintainable as you add more
A flow that works today becomes a liability if nobody can tell what it does in six months. Use a consistent naming convention (department, purpose, version number) and keep development, test and production environments separate wherever Power Platform environments are available to you.
Resist the urge to notify on every single step. One well-timed summary beats five pings nobody reads. For anything that needs to run longer than Power Automate’s limits comfortably allow, split the process: save state to a list or Dataverse table, end the run, and trigger a fresh one for the next phase.
Creative uses beyond the basics
Once the routine flows are running, there’s room to get more ambitious. AI Builder lets you add document processing to a flow, so instead of just saving an invoice attachment, you can extract the invoice number, amount and due date straight into SharePoint columns without anyone typing them in.
Approvals can get smarter too. Rather than a flat “approve or reject”, you can branch based on amount, so a £50 expense clears automatically while anything over a set threshold routes to a second approver. It’s a small change that saves managers from rubber-stamping low-risk requests all day.
Data visualisation is another natural extension. A weekly digest flow can push its summarised numbers into a Power BI dataset instead of just an email, giving you a dashboard that updates itself rather than a spreadsheet someone has to remember to refresh. None of this needs to happen on day one. Start with the seven flows above, get them stable, and layer in AI extraction or conditional approvals once the basics are earning their keep.
Security and compliance considerations
Every connection a flow uses inherits the permissions of whoever owns it, which means a flow built under someone’s personal account can quietly stop working the day they leave the business, or worse, keep running with access nobody remembers granting. A shared service account for anything business-critical avoids that trap.
Data loss prevention policies, set at the environment level, control which connectors can be used together, so a flow that tries to move data from SharePoint into a personal email account can be blocked before it ever runs. It’s worth checking these policies exist for any environment handling customer or financial data.
Keep an eye on where sensitive data actually travels. A flow that attaches customer documents to an email, for instance, is creating a copy outside your managed storage, which matters if you’re handling anything covered by data protection obligations. Where possible, link to a document rather than attaching it, and restrict who in the organisation can create or edit flows that touch sensitive lists.
Connecting flows to third-party services and APIs
Not every tool your business uses has a dedicated Power Automate connector, but that doesn’t rule it out. The HTTP action lets a flow call almost any REST API directly, which covers everything from a booking system to a marketing platform, provided you have the right authentication details.
This is also where webhook triggers earn their place. Instead of a flow polling a service every few minutes asking “anything new?”, a webhook lets the external service tell the flow the moment something happens, which is faster and lighter on action consumption. Marketing and lead tools are a common use case here: when a new enquiry lands in a form, a webhook can hand it straight to your flow for processing rather than waiting on a scheduled check. Our guide to automating marketing efforts covers this pattern in more depth if lead handling is where you’re starting.
Automated monitoring tools that sit outside Power Automate, such as aiMentions for tracking brand mentions across AI search tools, can also feed a flow through a webhook, turning an external alert into an internal Teams notification or a logged SharePoint entry.
Sharing and collaborating on flows with your team
A flow built in one person’s personal workspace is a flow that disappears the day they’re on holiday and something breaks. Building inside a shared Power Platform environment, with ownership assigned to a team rather than an individual, is the first fix.
Co-owners can be added to any flow so more than one person can edit, monitor and fix it. For anything used across a department, consider packaging related flows, connections and lists into a solution, which makes moving them between development and live environments far less fiddly than exporting one flow at a time.
Documentation doesn’t need to be elaborate. A short description field on the flow itself, noting what it does and who to contact if it breaks, saves whoever inherits it from having to reverse-engineer the logic from scratch.
What we’ve learnt building these for small businesses
We’ve set up versions of most of these flows for small business clients who were buried in manual admin, and the pattern is always the same: the flow itself is rarely the hard part. The real win comes from someone actually mapping the process first. Our work with Microsoft 365 and CRM automation, including our own SmartFlowCRM, has shown us that a flow handed over without documentation or a named owner tends to quietly stop working within months. If you don’t have the time or the admin permissions to build and maintain these yourself, that’s exactly the gap a managed implementation fills.
— Chris
Where TTOY Digital fits if you’d rather hand this off
If building and maintaining flows isn’t where you want to spend your week, we can take it on. Our CRM integration work connects forms, email and lead capture into SmartFlowCRM so nothing sits in an inbox waiting to be typed up, and our Microsoft 365 packages cover the licensing side too. It’s worth bringing in a specialist when the integration touches multiple systems, needs unattended automation, or simply when nobody on your team has a spare afternoon. Have a look at our web applications service if the flow needs its own front end.
FAQ
What are some cool things I can do with Power Automate?
You can automate document extraction with AI Builder, route approvals based on conditions like amount or department, and turn a weekly report into a live dashboard feed instead of a static email. These sit on top of simpler flows like attachment saving or lead capture once those are running reliably.
What are some examples of Power Automate projects?
Common projects include saving email or Forms attachments to SharePoint, routing leave and expense approvals, sending weekly digest summaries instead of constant notifications, and pushing new leads straight into a CRM. Onboarding checklists and scheduled file distribution are also popular starting points for small teams.
What are some common uses for Power Automate?
The most common uses are cutting out repetitive admin: filing attachments, chasing approvals, summarising activity, and moving data between Forms, SharePoint and a CRM without manual retyping. Most small businesses start with one or two of these before expanding into more advanced automation.
What are some tips and tricks for Power Automate?
Wrap risky actions in Try and Catch scopes with “Configure run after” so failures log to a list instead of going unnoticed, as Microsoft’s error handling guidance recommends. Batch actions where possible to stay within daily limits, and always build the simplest working version before adding branching logic.
