Audience: Business professionals who want to automate a repetitive task and have never built a flow.
Prerequisites: A work account that can open Power Automate and create a SharePoint list. Familiar with email and SharePoint or Lists.
License and software: Microsoft 365 work account that can open Power Automate and create a SharePoint list. Power Automate with standard connectors is included with most Microsoft 365 business and enterprise plans. No premium license.
YOU LEAVE WITH Two working flows: a notification and an approval.
BY THE END, STUDENTS WILL BE ABLE TO
-
Explain triggers, actions, connectors and dynamic content
-
Build an Issue Tracker list to use as a flow data source
-
Build an automated notification flow that puts data from the new item into an email
-
Use run history to find and fix an error
-
Build an approval flow with a condition that updates the item when the manager approves or rejects
Module 1: Foundations
-
When this happens, do that: the trigger and action pattern
-
Key terms: flow, trigger, action, connector, connection, dynamic content, run history
-
Flows run with the owner's credentials; automated versus instant flows
-
Confirm access to Power Automate and Microsoft Lists
-
Create the Issue Tracker list from the template and add four sample items
-
Labs 0 and 1: Validate access and create the Issue Tracker list
Module 2: Your First Automated Flow
-
Create an automated cloud flow with the When an item is created (SharePoint) trigger
-
Point the trigger at your list
-
Add Send an email (V2) and fill To, Subject and Body with dynamic content: Assigned to Email, Title, Priority, Created
-
Add an item to test the flow, then find the email
-
Read a successful run: trigger inputs and action outputs
-
Lab 2: Send an email when a new issue is created
Module 3: Reading Run History
-
Add a flawed condition and create an item with no Assigned To
-
Find the failed run and the step with the red mark
-
Read the error: 'To field cannot be null or empty'
-
Fix the logic and rerun the flow without entering new data
-
Confirm the rerun succeeds
-
Lab 3: Break the notification flow, find the error in run history and fix it
Module 4: Approvals and Conditions
-
Approval types and Approve/Reject - First to respond
-
Add an Approved Yes/No column to the list
-
Trigger on When an item is created or modified, and stop the flow from triggering itself again
-
Check for Critical priority, then Start and wait for an approval
-
Branch on the approval Outcome and update the item with Update item
-
Respond to the approval in Outlook, Teams or Power Automate Approvals
-
Lab 4: Send critical issues for manager approval