Automate the Mundane: Power Automate Starter Kit
3 workflows anyone can build, plus templates, best practice, and a path to certification
If you spend time copying data between spreadsheets, nudging teammates for approvals, or hunting across inboxes for updates, Microsoft Power Automate can give you hours back every week. This practical guide walks you through a beginner-friendly Starter Kit: three proven workflows you can build in under an hour, the guardrails to do it safely, and how to level up with training and certification. It’s designed for business users, not just IT.
Ready to go deeper? Explore Nexacu’s Power Automate courses delivered face-to-face across Australia or live online. If you’re working across Microsoft 365, you’ll also benefit from Power Platform training and companion Power BI analytics.
Jump to: Why automate • The Starter Kit • Workflow 1: Smart Approvals • Workflow 2: Email-to-SharePoint • Workflow 3: Teams Nudges • Security & governance • Useful expressions
Quick takeaways
- • Start small: one messy task → one clean flow. Build momentum.
- • Use Microsoft 365 context: Outlook, SharePoint, OneDrive, Teams, Planner.
- • Keep humans in the loop: Approvals and alerts prevent silent failures.
- • Log everything: add a SharePoint list to track runs, errors, and owners.
- • Secure by design: least privilege, data loss prevention (DLP), solution-based packaging.
What is Power Automate and why it matters
Power Automate is Microsoft’s low-code automation service for building “flows” that connect apps and data. It works across the Microsoft 365 stack and hundreds of connectors, so you can trigger actions on new emails, form submissions, file changes, or scheduled times. For most teams, the fastest wins come from automating repetitive touchpoints that happen daily: approvals, filing, notifications, reminders, and syncs.
Even a simple three-step flow can save minutes per task. Multiply that across a week and a team, and you’ll free hours for analysis, customer work, and creative problem-solving. If you’re new to automation, the best way to learn is to build a tiny but real workflow and ship it.
Your Starter Kit: 3 workflows anyone can build
Below are three beginner-friendly automations that fit most roles. Each one uses out-of-the-box connectors and takes advantage of Microsoft 365 apps you already have.
Workflow 1 — Smart Approvals in Teams and Outlook
Turn a messy email chain into a clean approval with audit trail. Use Approvals in Power Automate to push the request into Teams and email, collect a decision with comments, and log the result in SharePoint.
Steps to build:
- Create a SharePoint list “Approvals Log” with columns: Title, RequestedBy, DueDate, Status, Comments, RequestLink.
- In Power Automate, choose When a new item is created (SharePoint) as the trigger.
- Add action Start and wait for an approval → Approval type: Approve/Reject – First to respond.
- Notify approvers via Teams (Post adaptive card and wait for a response) and via Outlook (Send email (V2)).
- On approval, update the list item status to Approved and send a confirmation email.
- On reject, set status to Rejected, capture the comment, and notify the requester.
Good to know
- Approvals create an audit trail visible in Teams and the Approvals app.
- Use environment-level DLP so external connectors can’t siphon data.
Workflow 2 — Email to SharePoint: auto-file and tag
Stop dragging emails into folders. This flow watches a mailbox for key phrases or senders, saves the email and attachments to SharePoint, and adds consistent metadata for search and compliance.
Steps to build:
- Trigger: When a new email arrives (V3) with a subject filter like “Proposal” or from specific domains.
- Condition: if attachments exist, loop and save each file to a SharePoint library “Client Communications”.
- Create a SharePoint list item to log From, Subject, Received, and a link to the saved files.
- Send a Teams message to a channel with the link and key metadata.
Workflow 3 — Teams nudges: recurring task reminders that people welcome
Replace “just following up” emails with friendly, time-boxed nudges in Teams that link directly to the work. Great for weekly reports, roster checks, and shared inbox triage.
Steps to build:
- Trigger: Recurrence → set local time and cadence (e.g., weekly Fri 3:30pm).
- Action: Get items from a SharePoint list or Planner bucket to check outstanding tasks.
- Compose a summary with counts and due items (use Select and Join to format).
- Post a Teams channel message with next actions and links to items.
Security, governance, and “safe defaults”
Automation should reduce risk, not add it. Before you scale, align with IT and set simple guardrails:
- Use environments (Dev → Test → Prod) and package flows as Solutions.
- Apply DLP policies to keep business data inside Microsoft 365 unless explicitly approved.
- Create a Run Log list with flow name, status, owner, timestamp, and error detail.
- Turn on notifications for failed runs and set backup owners.
- Store secrets in Connections with least privilege; avoid hard-coding IDs.
Useful expressions for common tasks
These examples help with formatting dates, trimming long fields, and summarising lists. Add them to Expression fields inside your flow where needed.
Format date to AEST
formatDateTime(convertTimeZone(utcNow(),'UTC','AUS Eastern Standard Time'),'ddd, dd MMM yyyy h:mm tt')
Truncate long titles with ellipsis
if(greater(length(body('Get_item')?['Title']),80), concat(substring(body('Get_item')?['Title'],0,77),'...'), body('Get_item')?['Title'])
Join top 3 item titles with bullets
join(take(select(body('Get_items')?['value'], item()?['Title']), 3), ' • ')
Continue below for troubleshooting, measurement, more learning resources, use cases, FAQs, and the download CTA.
Troubleshooting and quality checks
- Silent failures: add a final Scope with Run after = has failed to send an alert to owners.
- Permissions errors: verify the SharePoint library/list permissions and the connection owner.
- Connector throttling: batch with Apply to each + concurrency control; add small delays if needed.
- Timezones: convert to your local zone before formatting timestamps.
- Sprawl: name flows consistently: [PA] Area — Purpose — Trigger → Outcome.
Prove value with simple metrics
Track three signals to show progress and secure buy-in:
- Time saved: minutes per run × runs per week × team size.
- Quality uplift: fewer missed approvals, consistent filenames/metadata, fewer reminders.
- Cycle time: measure approval/request turnaround before and after your flow.
Learn fast: courses and certification
Hands-on practice is the fastest way to build confidence. Choose a learning path that fits your role:
- Power Automate training (Nexacu) — beginner to advanced, live online or in-person across Australia.
- Microsoft Learn — Power Automate — free docs, modules, and reference.
- PL-900 & PL-100 — certifications for business users and app makers.
Download the Starter Kit — the three workflows with screenshots, expressions, and checklists.
Download PDF View course datesFive more ideas to automate in under an hour
- Forms → List: route Microsoft Forms submissions to SharePoint and notify a channel.
- Planner digest: weekly Planner summary to Teams with overdue items and owners.
- New file alert: when a proposal PDF is added to “Client Docs,” notify account manager and create a Planner task.
- Calendar handover: daily summary at 4pm posting tomorrow’s key meetings to a team channel.
- Contact sync: save flagged Outlook contacts into a Dataverse table or SharePoint list for team visibility.
Related learning at Nexacu
- Power Platform pathway — connect Automate with Power Apps and Dataverse.
- Power BI training — turn your automation logs into dashboards and alerts.
- Microsoft Teams training — make your automations visible where people work.
Frequently asked questions
Do I need admin rights to start?
No. Most Starter Kit flows use standard connectors available to business users. If you hit permission issues, ask IT to confirm your environment and DLP policies.
Will automations break if someone leaves?
Assign a backup owner and package flows as Solutions so they can be re-assigned. Store configuration in SharePoint lists rather than hard-coding IDs.
How do I keep flows tidy as we scale?
Name consistently, tag with owner and purpose, keep a Run Log list, and review monthly. Move team-critical flows to a managed environment with change control.
Where can I learn the expressions?
Use Microsoft’s functions reference. Our courses include a practical expressions cheat-sheet and exercises.
See Power Automate course dates Download the PDF guide
Note: Screens, names, and capabilities can vary by Microsoft 365 plan and tenant configuration. Confirm your organisation’s governance and DLP policies before connecting external services.
