100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace
Programming

Your First Flow

A step-by-step walkthrough of planning, building, testing, and turning on your first Power Automate cloud flow.

FoundationsBeginner9 min readJul 10, 2026
Analogies

Planning Before You Build

Before opening the designer, write down three things in plain language: the exact trigger event, the desired end result, and every system involved. For a common starter flow like "notify the team when a high-priority SharePoint list item is created," this means identifying the SharePoint site and list, the condition that defines "high-priority," and the Teams channel that should receive the notification, so the build maps directly onto that plan instead of being assembled ad hoc.

🏏

Cricket analogy: Planning a flow is like a captain setting a fielding plan before the first ball is bowled, deciding in advance exactly which field position responds to which type of delivery.

Building the Flow Step by Step

From make.powerautomate.com, choose Create, then Automated cloud flow, search for and select the "When an item is created" SharePoint trigger, and specify the site address and list name. Add a Condition action checking whether the Priority column dynamic content equals "High," and inside the Yes branch add a Teams "Post message in a chat or channel" action, using dynamic content to pull the item's Title and Created By fields directly into the message text.

🏏

Cricket analogy: This is like assembling a training drill step by step: set the bowling machine (trigger), add the coach's checkpoint on technique (condition), then the feedback call to the player (action) if the checkpoint fails.

text
Trigger: When an item is created (SharePoint)
  Site Address: https://contoso.sharepoint.com/sites/Support
  List Name: Escalations

Condition: Priority is equal to High
  If yes:
    Action: Post message in a chat or channel (Teams)
      Team: Support Escalations
      Channel: General
      Message: "New high-priority item: @{triggerOutputs()?['body/Title']} " &
                "created by @{triggerOutputs()?['body/Author/DisplayName']}"
  If no:
    (no action  flow ends)

Saving, Testing, and Turning It On

Click Save in the top-right corner to store the flow; the flow checker will flag any incomplete required fields before it lets you save. Use Test, then "Manually," and either create a real SharePoint item or supply sample trigger data to trace a full run through Run history. Once a run completes successfully end to end, the flow's toggle switches to On automatically, and from then on it fires in the background every time a matching SharePoint item is created, with no further action needed from you.

🏏

Cricket analogy: This is like a net session before the real match: a friendly practice ball run (test) confirms the technique works, and only then does the player get selected (turned on) for the actual game.

You can find your finished flow later under My flows, where columns show its status (On/Off), last modified date, and a 28-day run history chart. From there you can also share the flow with co-owners so others can edit or monitor it.

  • Plan a flow in plain language first: trigger, end result, and systems involved.
  • Automated cloud flows start from Create > Automated cloud flow in the designer.
  • Condition actions branch logic into Yes/No paths based on dynamic content values.
  • Dynamic content pulls trigger and action outputs directly into later steps' fields.
  • The flow checker blocks saving until required fields are complete.
  • Test a flow manually with real or sample trigger data and review Run history.
  • A flow's toggle switches to On after a successful run, and it then fires automatically going forward.

Practice what you learned

Was this page helpful?

Topics covered

#Programming#PowerAutomateStudyNotes#YourFirstFlow#Flow#Planning#Before#Build#StudyNotes#SkillVeris#ExamPrep