Microsoft Power Automate: Build your first automated workflow

Accessible summary

What this session covers

This enhanced session explains how to turn one bounded manual process into a tested and maintainable Power Automate flow. It starts with mapping the task in plain language, then covers flow patterns, triggers, actions, dynamic content, conditions, connections, testing, diagnosis and ownership.

• choosing a repetitive task with a clear trigger and safe result
• mapping the current process before opening the flow designer
• choosing between automated, instant and scheduled flows
• configuring a trigger and a short sequence of actions
• using dynamic content from earlier steps
• creating one clear condition with yes and no routes
• checking connections and permissions
• testing the intended route and important exceptions
• using Flow Checker and run history to diagnose problems
• documenting the flow and planning ownership and maintenance

Making the session work for you

The session is delivered through a Microsoft Teams webinar using PowerPoint Live. You can personalise how you follow and take part. The session is recorded, and you can watch rather than follow along unless the trainer asks you to try something.

• use live captions or translation from the three-dots menu
• choose a view that gives you the clearest layout
• use the presentation slider to zoom in or out
• keep your camera and microphone off unless invited
• use Q&A for questions and keep chat closed when not typing
• use reactions or another participation route if that works better for you
• share respectful feedback and use the key links provided in chat

Everyone can build confidence

The aim is to automate one small, recognisable process safely. A clear process map makes the flow easier to build, test, explain and maintain.

Navigator and WeChange.AI

Navigator is a personalised platform for WeChange.AI customers. It helps you find Microsoft 365 tools, resources and upcoming sessions relevant to your role.

Visit Navigator

WeChange.AI supports public and third sector organisations to use technology with confidence, purpose and impact.

Visit WeChange.AI

Key concepts

The challenge

Repeated manual steps can be delayed when the next action depends on memory or copying. Repetition can create missed notifications, inconsistent records or errors. Some exceptions still need human judgement. The session therefore follows one bounded task from its manual process to a tested, maintainable flow.

Your route through the session

• choose the task
• select the flow pattern
• configure the trigger and actions
• test and diagnose
• plan ownership

Choose a suitable task

• start with a routine Microsoft 365 task that follows a recognisable pattern
• identify what happens first, what repeats and what result should be produced
• keep exceptions and sensitive decisions with a person where judgement is required
• choose a bounded first automation that can be tested without disrupting live work

Map the manual process

• write the trigger that starts the process in one clear sentence
• list each action in the order a person currently completes it
• name the information that moves from one step into the next
• mark decisions, exceptions and failure points before opening the designer

Choose the flow pattern

• use an automated flow when an event in a connected service should start the process
• use an instant flow when a person should deliberately start the action
• use a scheduled flow when work should begin at a defined recurring time
• choose the pattern from the process need rather than from a template

Configure the trigger

• select the Microsoft 365 event that represents the real start of the process
• configure only the details needed to identify the right items
• check which connection and permissions the trigger uses
• test the trigger with safe data before adding unnecessary complexity

Add actions in sequence

• add each notification, task or record update in the order it must occur
• name steps clearly so another person can understand the flow later
• keep the first build short enough to test and diagnose confidently
• read the flow from top to bottom as a plain-language process story

Match the flow pattern to the starting event

• event in a connected service: automated flow, such as responding when an item is created or changed
• person deliberately starts it: instant flow, such as running a controlled action when needed
• defined time is reached: scheduled flow, such as completing routine work at an agreed interval

Use dynamic content

• select values produced by the trigger or a previous action
• check that each value represents the field expected by the destination step
• use clear sample data so names, dates and identifiers can be recognised
• avoid typing a fixed value when the process needs information from the current item

Use one clear condition

• state the question the flow must evaluate in plain language
• choose the value, comparison and expected result deliberately
• configure clear yes and no outcomes
• keep human review where the decision cannot be reduced safely to a rule

Check connections and permissions

• each connector uses a connection associated with an account or service
• the flow can act only through the access available to its connections
• a changed password, role or permission may cause a previously working step to fail
• review connections before wider use and avoid relying on one unavailable owner

Test the prepared route

• run the flow using safe, realistic information that should follow the intended route
• confirm that the trigger fired and each action received the expected values
• compare the result with the outcome defined at the start
• test important alternative or exception paths before relying on the workflow

Use Flow Checker

• review errors and warnings linked with individual steps
• open the affected trigger or action and inspect required settings
• correct the confirmed issue rather than changing unrelated parts of the flow
• run the checker again and complete a fresh test

Use run history as evidence

• open a completed or failed run instead of guessing why the result changed
• inspect step status, inputs and outputs in the order the flow ran
• find the first point where the actual result differs from the expected process
• correct the configuration or data issue, then repeat the same controlled test

Diagnose a failed run

• start with the visible error and the step where it occurred
• compare the failing input with the value the action expected
• check connections, permissions and missing or incorrectly typed information
• make one evidence-based correction and rerun the relevant test

Use a diagnosis checklist

• trigger: did the correct event start the flow
• step status: which action first failed or was skipped
• inputs: did the step receive the expected values
• outputs or error: what result or message explains the failure
• controlled retest: did one correction resolve the same scenario

Plan ownership and maintenance

• use a descriptive name that identifies the process and intended outcome
• record the trigger, main actions, dependencies and known exceptions
• add an appropriate co-owner or maintenance arrangement where needed
• review connections, failures and the process when ownership or organisational needs change

What the visuals and demonstrations showed

The visual sequence followed one routine task from a manual process map to a tested flow with documented ownership.

• identifying the trigger, repeated actions, result and human exceptions
• choosing an automated, instant or scheduled flow
• configuring the trigger with safe sample data
• adding a short sequence of clearly named actions
• selecting dynamic content from earlier steps
• creating one explicit condition with yes and no routes
• checking connections and permissions
• testing the intended route and an exception path
• using Flow Checker to inspect a configuration issue
• opening run history and reviewing step inputs and outputs
• finding the first failure point and making one correction
• recording ownership, dependencies and review needs

Key takeaways

• map the task before opening the flow builder
• name the trigger, repeated actions, result and human exceptions
• choose the flow pattern from how the process begins
• keep the first build short and reviewable
• use dynamic content instead of unnecessary fixed values
• use one clear condition and preserve human judgement
• test with safe data, Flow Checker and run history
• document the flow and plan who will maintain it

A dependable Power Automate journey

• choose a bounded repetitive task
• map the manual process
• select the flow pattern
• configure the trigger, actions, dynamic content and condition
• test the prepared and exception routes
• diagnose from Flow Checker and run evidence
• document and assign ownership

Actions you can take

Try the tip of the month

This session’s tip: map the manual process in plain language before you open the flow builder

How to do it: list the steps in order, identify the trigger and repeated actions, name the result and flow pattern, and mark the exceptions that remain a human decision

Why it matters: a clear map shows what the flow must do and keeps judgement with a person

Try it now: map one routine task by naming its trigger, actions, result and exceptions

Build confidence with one practical route

• choose one routine Microsoft 365 task
• write the trigger in one sentence
• list the current actions in order
• identify information that moves between steps
• mark decisions and exceptions that stay with a person
• select the automated, instant or scheduled pattern
• build a short test version
• run Flow Checker
• complete one controlled test
• inspect run history and document the result
• name the owner and next review point

Questions and feedback

Questions are welcome. If something is unclear, ask for it to be explained another way or demonstrated again.

Complete the Support and Skilling Week feedback form

Contact WeChange.AI

For skilling queries, email training@wechange.ai.

Andrew Boxall, Managing Director: andrew@wechange.ai

Paul Ford, Industry Director for Education and Philanthropies: paul@wechange.ai

Josh Wilson, Industry Specialist: josh@wechange.ai

Elle Avilla, Customer Success and Delivery Skilling Lead: elle@wechange.ai

Izzy Pochin, Resources and Accessibility Lead: izzy@wechange.ai

Activity sheet

Follow one routine Microsoft 365 task from its manual process through trigger, actions, dynamic content, a condition, controlled testing and maintainable ownership.

How to use this activity sheet

This sheet supports Session 19: Microsoft Power Automate. Use it after the live session, or follow selected steps while your trainer demonstrates one bounded workflow from process map to tested result.

• work at your own pace and pause after each activity
• use safe practice data and a bounded test process
• map the process before opening the flow designer
• keep exceptions and sensitive decisions with a person where judgement is required
• make one evidence-based change at a time when diagnosing a failure

What you will achieve

• choose a repetitive task with a clear trigger and safe result
• map the manual process in plain language
• choose an automated, instant or scheduled flow from how the process begins
• configure the trigger and check its connection and permissions
• add a short sequence of clearly named actions
• use dynamic content from earlier steps
• create one explicit condition with clear yes and no routes
• test the intended and important alternative paths
• use Flow Checker to identify confirmed configuration issues
• use run history, step inputs and outputs to find the first failure point
• document dependencies, exceptions and maintenance arrangements
• assign proportionate ownership before wider reliance

Your learning route

Stage	You will practise
1. Choose the task	repetition, trigger, result and human exceptions
2. Map the process	ordered actions, information and failure points
3. Choose the pattern	automated, instant or scheduled
4. Build	trigger, actions, dynamic content and condition
5. Test	safe data, intended route and alternatives
6. Diagnose	Flow Checker, run history, inputs and outputs
7. Maintain	connections, documentation and ownership

Before you start

• sign in to the Power Automate environment provided by your organisation
• choose one routine Microsoft 365 task you are authorised to practise
• prepare safe, recognisable sample data
• identify the person who would decide any exception
• avoid changing a live process during practice
• allow about 45 to 60 minutes, or complete one activity at a time

Notice: Connectors, flow creation, sharing and run information depend on organisational access, permissions and settings. Complete only the activities available and authorised in your environment.

Activity 1: Choose a suitable first automation

Outcome: Select a repeated task with a recognisable beginning, bounded steps and a safe result.

1. Name the repeated Microsoft 365 task.
2. Write what happens first.
3. Identify the actions currently repeated by a person.
4. Name the result the process should produce.
5. List any exception or sensitive decision that must remain human-owned.
6. Choose a test that will not disrupt live work.

Suitability check	Your answer
repeated task
first event
repeated actions
intended result
human exception or decision
safe test boundary

Pause and check

• the task follows a recognisable pattern
• the result can be checked
• judgement has not been automated

Activity 2: Map the manual process as a story

Outcome: Describe the process clearly before building it in the designer.

7. Write the trigger in one sentence.
8. List the actions in the order a person completes them.
9. Name information that moves from one step into the next.
10. Mark decisions and exceptions.
11. Mark likely failure points.
12. Read the complete map as a plain-language story.

Process part	Your description
trigger
action 1
action 2
information passed onwards
decision or exception
failure point
final result

Pause and check

• steps are in sequence
• moving information is visible
• exceptions and failure points are explicit

Activity 3: Choose the flow pattern

Outcome: Match the flow design to how the real process begins.

Process begins when	Flow pattern	Your example
an event occurs in a connected service	automated
a person deliberately starts it	instant
a defined recurring time is reached	scheduled

13. Return to the first event in the process map.
14. Choose automated, instant or scheduled.
15. Explain why another pattern would be less suitable.
16. Keep the choice based on process need rather than an available template.

The pattern I chose: ____________________________________________________________________

My reason: ____________________________________________________________________

Pause and check

• the pattern matches the true start
• the choice is not template-led
• the result remains safely testable

Activity 4: Configure the trigger

Outcome: Represent the genuine start event and verify the connection being used.

17. Select the Microsoft 365 event that starts the process.
18. Configure only details needed to identify the correct items.
19. Check the account or service connection.
20. Check the permissions available to that connection.
21. Use safe data to test the trigger before adding complexity.
22. Confirm that the correct event started the flow.

Trigger check	Your finding
service or connector
event
identifying details
connection
permission consideration
safe test result

Pause and check

• the trigger represents the real start
• the connection is identifiable
• the correct event fired

Activity 5: Add and name the actions

Outcome: Build a short sequence that another person can read and understand.

23. Add the first notification, task or record update.
24. Add the next required action.
25. Keep the first build short.
26. Rename steps so they explain their purpose.
27. Read the flow from top to bottom.
28. Remove an action not required for the first test.

Step	Purpose	Clear name
action 1
action 2
optional action 3

Pause and check

• actions appear in the required order
• step names explain the process
• the first build remains diagnosable

Activity 6: Use dynamic content deliberately

Outcome: Carry the correct information from the trigger or an earlier action into the next step.

29. Choose one destination field in an action.
30. Select the value produced by the trigger or a previous action.
31. Check that the selected value matches what the destination expects.
32. Use recognisable sample names, dates or identifiers.
33. Replace a fixed practice value where the current item should supply the information.
34. Run a controlled test and inspect the value received.

Destination field	Dynamic value	Source step	Expected sample

Pause and check

• each value comes from the intended step
• data meaning matches the destination
• fixed text is not used where current data is required

Activity 7: Add one clear condition

Outcome: Create two explicit routes while keeping non-rule-based judgement with a person.

35. State the question the flow will evaluate in plain language.
36. Choose the value.
37. Choose the comparison.
38. Choose the expected result.
39. Configure the yes route.
40. Configure the no route.
41. Confirm that neither route is ambiguous.
42. Leave any decision that cannot be reduced safely to a rule with a person.

Condition part	Your choice
plain-language question
value
comparison
expected result
yes route
no route
human review retained for

Pause and check

• the rule can be stated clearly
• both routes have an outcome
• human judgement remains where needed

Activity 8: Review connections and permissions

Outcome: Understand which accounts or services allow the flow to reach each system.

43. List the connector used by each step.
44. Identify the associated connection.
45. Check that the connection has the required access.
46. Consider what would happen after a password, role or permission change.
47. Identify whether the flow relies on one unavailable owner.
48. Record a maintenance action before wider use.

Dependency	Your finding
connector and connection
required access
change that could cause failure
single-owner risk
maintenance action

Pause and check

• connections and access are visible
• ownership risk is recognised
• wider reliance is not based on an unavailable person

Activity 9: Test the intended route

Outcome: Prove the prepared scenario and compare the result with the outcome defined at the start.

49. Use safe, realistic test information.
50. Run the flow.
51. Confirm that the trigger fired.
52. Confirm that each action received expected values.
53. Check which condition route ran.
54. Compare the final result with the intended outcome.
55. Record what this test does not prove.

Test check	Your finding
test information
trigger result
action values
condition route
final result
case not yet tested

Pause and check

• the prepared path completed as expected
• the final result matches the defined outcome
• one successful run is not treated as proof of every case

Activity 10: Test alternatives and exceptions

Outcome: Check important routes before relying on the workflow.

56. Choose a safe example for the alternative condition route.
57. Choose an important exception from the process map.
58. Run one scenario at a time.
59. Check whether the expected branch or human route is used.
60. Confirm that no live or sensitive action was triggered.
61. Record any untested case that still prevents wider use.

Scenario	Expected route	Observed result	Action
alternative condition
important exception

Pause and check

• both condition routes were considered
• exceptions do not bypass human judgement
• remaining test gaps are visible

Activity 11: Use Flow Checker

Outcome: Correct a confirmed configuration issue without changing unrelated parts of the flow.

62. Open Flow Checker.
63. Review errors and warnings linked to individual steps.
64. Open the affected trigger or action.
65. Inspect the required setting.
66. Correct the confirmed issue.
67. Run Flow Checker again.
68. Complete a fresh test.

Checker finding	Affected step	Correction	Retest result

Pause and check

• the issue was linked to a specific step
• unrelated steps were not changed
• the checker and test were rerun

Activity 12: Diagnose with run history

Outcome: Use execution evidence to find the first point where actual behaviour differs from the process map.

69. Open a completed or failed run.
70. Read step status in order.
71. Inspect the trigger details.
72. Inspect step inputs.
73. Inspect step outputs or error details.
74. Find the first point of difference.
75. Correct the configuration or data issue.
76. Repeat the same controlled test.

Evidence	Question	Your finding
trigger	did the correct event start the flow?
step status	which action first failed or was skipped?
inputs	did the step receive expected values?
outputs or error	what explains the result?
controlled retest	did one correction resolve the same scenario?

Pause and check

• diagnosis used run evidence
• the first difference was identified
• the same scenario was retested

Activity 13: Diagnose a prepared failure

Outcome: Practise one evidence-based correction safely.

77. Start with the visible error and affected step.
78. Compare the failing input with the expected value.
79. Check the connection and permissions.
80. Check missing or incorrectly typed information.
81. Choose one evidence-based correction.
82. Rerun the relevant test.
83. Record whether the same failure is resolved.

The visible error: ____________________________________________________________________

The first failure point: ____________________________________________________________________

The expected and actual input: ____________________________________________________________________

The single correction: ____________________________________________________________________

The retest result: ____________________________________________________________________

Pause and check

• the error was not guessed from the final outcome alone
• only one correction was made
• the result was verified in a new run

Activity 14: Document and assign ownership

Outcome: Make the flow understandable and maintainable after the initial build.

84. Give the flow a descriptive name identifying process and outcome.
85. Record the trigger.
86. Record the main actions and condition.
87. Record connections and dependencies.
88. Record known exceptions and untested cases.
89. Name the accountable owner.
90. Add an appropriate co-owner or maintenance arrangement where required.
91. Choose when connections, failures and the process will be reviewed.

Maintenance record	Your entry
flow name
trigger
main actions and condition
connections and dependencies
known exceptions or gaps
owner or co-owner
review point

Pause and check

• another authorised person can understand the flow
• dependencies and exceptions are documented
• ownership and review are explicit

Put it into practice: build one bounded workflow

Scenario: A team manually copies details from a new Microsoft 365 item into a notification and records whether it needs a standard or human-reviewed route.

• define the safe result and human exception
• map the trigger, repeated actions, information and failure points
• choose the flow pattern
• configure the trigger and verify its connection
• add and name the actions
• insert dynamic content from the current item
• add one clear condition with yes and no routes
• test the intended, alternative and exception scenarios
• use Flow Checker and run history to diagnose evidence
• document the flow, dependencies, ownership and review point

The task and result: ____________________________________________________________________

The trigger and pattern: ____________________________________________________________________

The actions and dynamic content: ____________________________________________________________________

The condition and human exception: ____________________________________________________________________

The test and diagnosis: ____________________________________________________________________

The owner and review point: ____________________________________________________________________

Quick reference: choose the Power Automate route

If you need to…	Try…
start when a connected event occurs	an automated flow
start deliberately when needed	an instant flow
start at a recurring time	a scheduled flow
carry information forward	dynamic content from the trigger or an earlier action
create two rule-based routes	a condition with explicit yes and no outcomes
identify configuration issues	Flow Checker
understand an actual run	run history, step inputs and outputs
find a failure safely	locate the first difference and make one correction
protect continuity	document connections, exceptions, owner and review point

Your three takeaways

My most useful learning: ____________________________________________________________________

What I will implement: ____________________________________________________________________

What I will explore further: ____________________________________________________________________

If you need help

• name the flow, trigger, action, condition or failed step involved
• state the expected result and observed result
• note the exact visible error and relevant run details
• ask your local support route about connectors, permissions, ownership or unavailable features
• avoid sharing screenshots containing personal, confidential or sensitive information

Confidence grows through a controlled automation journey: map the task, build the smallest useful flow, test with evidence, diagnose the first failure point and maintain clear ownership.

Reflective journal

Why we ask you to reflect

Continuing Professional Development (CPD) is formative and it is about what it achieves for you and your organisation.

Instead of formally assessing your learning, we ask you to write a reflective note. This should reflect on how the learning was relevant and how it will impact your working practices.

Taking time to reflect on your learning makes it more likely you will embed it in your future practice.

What to cover and when

What your reflection should cover

• how the learning was relevant to you
• how the learning will impact your practice

When to complete it

Reflect as soon as possible following the skilling session. This keeps your note contemporaneous (written close to the time) and meaningful. Fill it in on your device, so the boxes expand as you type.

Topic	What to know
Timing	Complete the note as soon as possible after the training event.
Purpose	To embed the learning within your subsequent practice.
Focus	How the learning was relevant and how it will impact your practice.

Your reflective note

Complete each row below. Write in your own words. Your notes are private to you unless you choose to share them.

Prompt	Your response
Skilling session title
Date of the skilling session
Date you completed this note
How was the learning relevant to you and your work?
How will the learning impact your practice?

Recommended resources

These curated resources accompany the WeChange.AI skilling offer of Continuing Professional Development (CPD) accredited, and non-accredited, sessions. Use them before a session to build familiarity, or afterwards to revisit and apply the learning in day-to-day work.

Alongside these resources, Navigator helps WeChange.AI customers find personalised recommendations and available learning on Microsoft 365 tools, accessibility and AI relevant to their role. Returning to Navigator after a session can help you connect new knowledge with practical workplace needs, choose a useful next step and keep learning visible as confidence grows.

• Power Automate: Explore how it connects apps and services to automate repetitive tasks

An introduction to Power Automate and the kinds of flows you can build. A useful starting point before you choose a first task to automate.

• Microsoft Learn: Complete the beginner module Get started with Power Automate

A short training module covering creating a cloud flow, recurring flows, monitoring incoming email and sharing flows. It also includes a unit on troubleshooting flows.

• Power Automate: Follow the tutorial to create, test and run your first cloud flow

A step-by-step tutorial that builds a scheduled flow, tests it, then runs it. It offers a route using Copilot and a route without it.

• Power Automate: Connect flows to Microsoft Lists and SharePoint for request-based processes

Explains how to build connected workflows around request information stored in Lists or SharePoint. Useful for seeing how a flow fits into a wider process.

• Microsoft Forms, Excel and Power Automate: Send form responses to a spreadsheet automatically

Explains how to collect structured information in Forms and have it flow into Excel through Power Automate. A practical first automation to try.