7 Power Automate Flows Every Office Team Should Build This Week

The Scenario: The Overloaded Project Coordination Team

Picture a project coordination team managing internal projects:

• They track tasks in a SharePoint list.
• They share updates in Teams.
• They store documents in OneDrive.
• They report status in a monthly Power BI dashboard.

They’re drowning in:

• Late status updates.
• Missing documents.
• Forgotten approvals.
• Manual data exports.

We’ll use this team as our running example. Assume they already have:

• A SharePoint list named ProjectTasks.
• A Teams channel named Projects – Coordination.
• A OneDrive folder named Project Documents.
• A Power BI dataset refreshed from their project data.

Now let’s build the 7 Power Automate flows every office team like this should have.

1. Daily Task Digest to Teams Instead of 20 Status Emails

Before: Everyone sends individual status emails. The coordinator spends half an hour each morning piecing together what’s due.

After: A single daily digest message in Teams summarising tasks due today and overdue items.

What this flow does

• Runs every weekday at 8:30 AM.
• Pulls tasks due today and overdue from ProjectTasks.
• Posts a formatted summary in the Projects – Coordination Teams channel.

Key steps

1. Trigger

   • Use Recurrence trigger.
   • Set to every weekday at 08:30.

2. Get tasks

   • Action: Get items (SharePoint) on ProjectTasks.
   • Use an OData filter on DueDate and Status:

DueDate le '@{utcNow()}' and Status ne 'Completed'

3. Compose summary text
   • Use Select and Join actions to build a markdown-style list:

concat(
  '- ', Title,
  ' (Owner: ', AssignedTo.DisplayName,
  ', Due: ', formatDateTime(DueDate, 'yyyy-MM-dd'), ')
'
)

4. Post to Teams
   • Action: Post message in a chat or channel (Teams).
   • Channel: Projects – Coordination.
   • Message body: include the composed summary.

Why it matters

• Everyone sees the same list at the same time.
• No more “I didn’t see that email” excuses.
• Coordinator’s manual morning triage disappears.

2. Auto-Create Tasks from Meeting Notes in OneDrive

Before: Meeting notes get typed up and saved, then forgotten. Action points never make it into the task system.

After: Any bullet point in a notes file tagged @task becomes a SharePoint task automatically.

What this flow does

• Triggers when a notes file is updated in the Project Documents folder.
• Parses lines containing @task.
• Creates tasks in ProjectTasks with owner and due date if provided.

Notes file format

The team agrees to write notes like:

• @task Prepare slide deck | owner: Alex | due: 2026-10-15
• @task Confirm budget with finance

Key steps

1. Trigger

   • Action: When a file is modified (OneDrive).
   • Scope: Project Documents folder.

2. Get file content

   • Action: Get file content.

3. Split content into lines

   • Action: Compose with expression:

split(body('Get_file_content'), '
')

4. Filter task lines

   • Action: Filter array where contains(item(), '@task').

5. Parse each task line (inside Apply to each)

   • Use Compose and Split to separate title, owner, due date.

Example expression to get title:

trim(replace(item(), '@task', ''))

6. Create SharePoint task
   • Action: Create item (SharePoint) on ProjectTasks.
   • Map parsed values to Title, AssignedTo, DueDate.

Why it matters

• No extra work for the note taker.
• Action points move straight from notes to the task list.
• The team starts trusting that meeting decisions turn into trackable work.

3. Approval Flow for New Project Requests

Before: New project requests arrive via email or chat, get forwarded around, and approvals are buried in threads.

After: A simple approval flow with a clear audit trail and automatic notifications.

What this flow does

• Triggers when a new item is added to a ProjectRequests SharePoint list.
• Sends an approval request to the manager.
• On approval: updates status, posts to Teams, and creates a task.
• On rejection: updates status and notifies requester.

Key steps

1. Trigger

   • When an item is created (SharePoint) on ProjectRequests.

2. Start approval

   • Action: Start and wait for an approval.
   • Type: Approve/Reject – First to respond.
   • Details: include project name, description, estimated effort.

3. Condition on outcome

   • If Outcome is Approve:
     • Update Status to Approved.
     • Post message in Teams with key details.
     • Create initial planning task in ProjectTasks.
   • If Outcome is Reject:
     • Update Status to Rejected.
     • Send email to requester with comments.

Why it matters

• Approvals are visible and trackable.
• No more searching email history to find who said yes.
• The moment a project is approved, planning work starts automatically.

4. Document Naming and Filing Bot for Project Files

Before: Files are named Final_v3_new_FINAL2.pptx and dumped into random folders. People waste time hunting for the right version.

After: A flow standardises file names and moves them into the correct project folder based on metadata.

What this flow does

• Triggers when a file is created in a “Dropzone” folder.
• Renames the file based on project ID and document type.
• Moves it to the correct project subfolder.

Naming convention

The team agrees on:

• ProjectID_DocType_YYYYMMDD.ext

Example: PRJ-0123_StatusReport_20261005.xlsx.

Key steps

1. Trigger

   • When a file is created (OneDrive) in Project Documents/Dropzone.

2. Get file properties

   • Use metadata or parse from filename, e.g. PRJ-0123_StatusReport_raw.pptx.

3. Build new filename

concat(
  variables('ProjectID'), '_',
  variables('DocType'), '_',
  formatDateTime(utcNow(), 'yyyyMMdd'),
  '.',
  variables('Extension')
)

4. Move and rename file
   • Action: Move file to Project Documents/PRJ-0123/.
   • Set new name using the expression above.

Why it matters

• Everyone knows where the latest version lives.
• Faster onboarding for new team members.
• Cleaner SharePoint/OneDrive structure without manual policing.

5. Power BI Refresh Alerts When Data Fails or Looks Wrong

Before: The monthly dashboard sometimes silently fails to refresh, or data looks off. The team notices only when someone complains.

After: A flow monitors refresh status and basic data sanity, then alerts the team.

What this flow does

• Triggers on a schedule after the Power BI dataset refresh window.
• Calls the Power BI API to check latest refresh status.
• Optionally runs a simple check on key metrics via a stored procedure or endpoint.
• Posts a success/failure message in Teams.

Key steps

1. Trigger

   • Recurrence: daily at 07:15, after scheduled refresh.

2. Check refresh status

   • Action: Power BI – Get dataset refresh history.
   • Filter for latest entry.

3. Condition

   • If Status is not Completed:
     • Post a Teams message tagging the data owner.
   • Else:
     • Optionally call an Azure Function / API to validate key metrics.

Example of a simple validation query if you use SQL as a source:

SELECT
    COUNT(*) AS TaskCount,
    SUM(CASE WHEN Status = 'Overdue' THEN 1 ELSE 0 END) AS OverdueCount
FROM dbo.ProjectTasks
WHERE DueDate <= CAST(GETDATE() AS date);

4. Post summary
   • Teams message with:
     • Refresh status.
     • Row counts or key metric values.
     • Link to the report.

Why it matters

• Data issues are caught before stakeholders see the report.
• The team stops relying on “I hope it refreshed” as a strategy.

6. Smart Reminders Only for Truly Stale Tasks

Before: People ignore generic reminders because they fire for everything, including tasks that are already being worked on.

After: A flow sends targeted reminders only for tasks that are both overdue and untouched for a defined period.

What this flow does

• Runs daily.
• Finds tasks where:
  • Status is not Completed.
  • DueDate is in the past.
  • LastModified is older than X days.
• Sends a personalised reminder to the task owner.

Key steps

1. Trigger

   • Recurrence: daily.

2. Get items

   • Get items (SharePoint) on ProjectTasks.
   • OData filter example:

Status ne 'Completed' and DueDate lt '@{utcNow()}'

3. Filter for inactivity
   • Use Filter array with expression:

lessOrEquals(
  addDays(item()?['Modified'], 7),
  utcNow()
)

4. Send reminder (Apply to each)
   • Action: Send email (V2) or Send Teams message to AssignedTo.
   • Include:
     • Task title.
     • Original due date.
     • Link to the item.

Why it matters

• People see fewer, more relevant reminders.
• The coordinator stops manually chasing stale items.
• Overdue tasks get attention without spamming the whole team.

7. Weekly Summary Export to Excel for Management

Before: The coordinator spends Friday afternoons exporting SharePoint lists to Excel, cleaning them, and emailing management.

After: A flow builds a clean Excel file in a standard format and drops it into a shared folder automatically.

What this flow does

• Runs every Friday at 16:00.
• Pulls key fields from ProjectTasks and ProjectRequests.
• Writes them into an Excel file with defined tables.
• Sends a link to the management group.

Excel structure

• File: Weekly_Project_Summary.xlsx.
• Tables:
  • Tasks (TaskID, Title, Owner, Status, DueDate).
  • Requests (RequestID, Title, Status, ApprovedDate).

Key steps

1. Trigger

   • Recurrence: weekly, Friday 16:00.

2. Get data

   • Get items (SharePoint) from both lists.

3. Create or update Excel file

   • If you use a template:
     • Action: Copy file from template to Reports/Weekly with current date.
   • Use Add a row into a table (Excel Online) for each item.

Example: mapping a task to the Tasks table via Power Automate is configuration, but this is how the data might look in Excel:

' Example of how the resulting Excel table might be used in VBA later
Sub FilterOverdueTasks()
    With ThisWorkbook.Worksheets("Tasks").ListObjects("Tasks")
        .Range.AutoFilter Field:=5, Criteria1: "<" & Date
    End With
End Sub

4. Notify management
   • Action: Send email (V2) to a distribution list.
   • Include link to the file in SharePoint/OneDrive.

Why it matters

• The coordinator gets their Friday afternoon back.
• Management receives a consistent, clean report every week.
• The data pipeline from operations to oversight is stable and boring (in a good way).

One Concrete Next Step

Pick one pain point your team feels most often—daily status chaos, missing approvals, file mess, or manual reporting—and build just one of these flows this week. Once people see that Power Automate can remove a tedious part of their day without changing tools, it’s much easier to get buy-in for the rest.