Power Automate Tutorial: 3 Flows to Build Today

Most Power Automate tutorials stop at screenshots of the interface and never show you a finished, working flow. That gap leaves teams stuck between "I know what Power Automate is" and "I actually built something useful." This Power Automate tutorial closes that gap with three complete walkthroughs you can follow right now: auto-saving email attachments, routing manager approvals, and posting daily reports to Teams. Each one starts at the Create button and ends with a successful test run.

What Is a Power Automate Flow?

A Power Automate flow is an automated workflow that connects your apps, files, and services so they work together without manual effort. Every flow starts with a trigger (the event that kicks things off) and includes one or more actions (the steps that happen next).

For example, when a new email arrives in Outlook (trigger), Power Automate saves the attachment to SharePoint and posts a notification in Teams (actions). Microsoft includes Power Automate in every Microsoft 365 Business Basic, Business Standard, and Business Premium subscription, so you likely already have access.

Before You Start: Access and Permissions

Before building your first flow, confirm two things. First, open make.powerautomate.com and sign in with your Microsoft 365 work account. If the dashboard loads, you have a valid license. Second, check with your IT team that the connectors you need (Outlook, SharePoint, Teams) are not blocked by a data loss prevention (DLP) policy at the tenant level.

Understanding Flow Types

Power Automate offers three main flow types for cloud-based automation:

• Automated cloud flows run when a trigger event occurs, such as receiving an email or a file upload.
• Instant cloud flows run when you press a button, either in the Power Automate app or a custom Power App.
• Scheduled cloud flows run on a recurring schedule you define, such as every Monday at 9 AM.

This tutorial focuses on automated and instant cloud flows because they cover the majority of business use cases.

Tutorial 1: Auto-Save Email Attachments to SharePoint

This is the most requested beginner flow. It eliminates the manual process of downloading attachments and uploading them to your document library.

Step-by-Step Build

1. From the Power Automate dashboard, select Create and then Automated cloud flow.
2. Name your flow "Save Outlook Attachments to SharePoint."
3. Search for the trigger When a new email arrives (V2) under the Office 365 Outlook connector. Select it.
4. In the trigger settings, set Only with Attachments to Yes and Include Attachments to Yes.
5. Add a new step. Search for Apply to each and select it. Set the input to the Attachments dynamic content from the trigger.
6. Inside the Apply to each loop, add the action Create file from the SharePoint connector.
7. Set the Site Address to your SharePoint site, choose the Folder Path (for example, /Shared Documents/Email Attachments), and map File Name to the attachment name and File Content to the attachment content bytes.
8. Click Save, then Test. Choose Manually and send yourself a test email with an attachment.

If the test succeeds, you will see a green checkmark on every step. The attachment appears in your SharePoint folder within seconds.

Related: New to Power Automate? Read our companion guide on how to use Power Automate for an overview of the platform, licensing tiers, and five ready-to-run business workflows.

Tutorial 2: Build a Manager Approval Flow

Approval workflows replace email chains with a structured process. This flow routes a request to a manager and records the outcome automatically.

Step-by-Step Build

1. Select Create and then Instant cloud flow. Name it "Manager Approval Request."
2. Choose the trigger Manually trigger a flow. Add two text inputs: Request Title and Request Details.
3. Add the action Start and wait for an approval. Set Approval type to Approve/Reject - First to respond.
4. Enter the Title (use the Request Title input), Assigned to (your manager's email), and Details (use the Request Details input).
5. Add a Condition action. Set it to check whether the Outcome equals "Approve."
6. In the If yes branch, add Send an email (V2) to notify the requester of approval.
7. In the If no branch, add another Send an email (V2) to notify the requester of rejection, including the approver's comments.
8. Save and test. Trigger the flow manually, approve from the Approvals center in Teams, and confirm both emails are sent.

This pattern scales to any scenario: purchase orders, time-off requests, document sign-offs, or vendor onboarding. Change the trigger to a Microsoft Form submission or a SharePoint list item and the rest of the flow stays the same.

Tutorial 3: Daily Report from SharePoint to Teams

Scheduled flows are ideal for recurring tasks. This flow queries a SharePoint list every morning and posts a summary to a Teams channel.

Step-by-Step Build

1. Select Create and then Scheduled cloud flow. Name it "Daily Task Summary."
2. Set the schedule to run at 8:00 AM every weekday. Choose your time zone.
3. Add the action Get items from the SharePoint connector. Point it to your task list and add a filter query such as Status eq 'Open' to pull only active items.
4. Add a Select action to map each item into a simple format: Task Name, Assigned To, and Due Date.
5. Add a Create HTML table action using the output of the Select step.
6. Add Post message in a chat or channel from the Teams connector. Choose your target channel and paste the HTML table output into the message body.
7. Save and run a manual test to verify the table renders correctly in Teams.

Your team now receives a clean task summary every morning without anyone opening SharePoint. If your team is still getting comfortable with Teams, our guide on how to create a team in Microsoft Teams covers the fundamentals.

Need help connecting your business tools? Always Beyond builds and manages Power Automate workflows as part of our managed IT services. We handle the setup, testing, and ongoing support so your team can focus on results.

Use Copilot to Build Flows with Plain English

Microsoft's Copilot integration in Power Automate lets you describe a workflow in natural language and have the platform generate the flow structure for you. This feature is available in the cloud flow designer for tenants with Copilot enabled.

How It Works

1. On the Power Automate homepage, select Describe it to design it (or select Create and then choose Chat with Copilot about my idea).
2. Type a description of your workflow. For example: "When a Microsoft Form is submitted, send an approval to my manager. If approved, add a row to a SharePoint list and send a confirmation email."
3. Copilot generates a suggested flow with the trigger and actions pre-configured. Review each step and adjust any parameters such as email addresses, list names, or channel targets.
4. Select Create flow to open it in the designer where you can refine the details.

Copilot works best when your description is specific. Include the app names, the trigger event, and the desired outcome. Vague prompts like "automate my tasks" produce generic results. According to Microsoft's documentation, Copilot can also edit existing flows, answer questions about what a flow does, and help troubleshoot errors directly inside the designer.

Troubleshooting Common Flow Errors

Even well-built flows encounter issues. Here are the most common problems and how to fix them quickly.

Why Is My Flow Not Triggering?

Check three things: the trigger conditions match the actual event, your connections are authenticated (go to More > Connections and fix any broken links), and your tenant's DLP policies allow the connectors you are using. If the flow was working and stopped, try toggling the flow off and back on.

How Do I Fix Authentication Errors?

Authentication errors usually mean a token has expired or permissions have changed. Navigate to your connections in Power Automate, find the failing connection, and re-authenticate. If your organization uses conditional access policies, confirm that Power Automate is an approved app. For more context on conditional access, see our post on what is conditional access.

What If a Flow Times Out?

Cloud flows have a 30-day maximum duration for approval-based flows and a shorter window for most actions. If a flow times out, break long-running processes into smaller child flows or use the Configure run after setting to handle timeouts gracefully rather than letting the entire flow fail.

Next Steps After Your First Flows

Three tutorials are enough to build real momentum. From here, expand your skills by exploring templates in the Power Automate gallery, which offer pre-built flows for common scenarios like syncing Planner tasks with Outlook or backing up OneNote notebooks. Add error handling using scope actions and the try-catch-finally pattern to make your flows production-ready.

As your team adopts more flows, establish naming conventions and document each workflow so anyone can maintain them. The businesses that get the most value from Power Automate treat it as infrastructure, not a side project.

Ready to automate beyond the basics? Always Beyond helps small and mid-size businesses design, build, and manage Power Automate workflows that connect Microsoft 365 to the rest of your tech stack. Book a free consultation and let our team handle the complexity.