5 Microsoft Teams Automations That Save Hours Every Week
Practical Power Automate flows for Microsoft Teams — from turning meeting notes into Planner tasks to sending rich Adaptive Card approvals without leaving Teams.
Microsoft Teams is where most M365 organisations do their daily work. But Teams alone is a passive communication tool — it records what happened, not what needs to happen next. Power Automate bridges that gap, turning Teams conversations, messages, and meetings into structured actions without requiring anyone to copy things between systems. Here are five automations that have the highest impact-to-effort ratio for most teams, with step-by-step implementation guidance.
What You Need Before You Start
-
1Identify automation opportunities in Teams
Audit: channel message workflows, meeting scheduling, bot integrations, file management. Prioritise high-frequency, repetitive tasks (notifications, approvals, data entry).
-
2Create a Teams bot or use connectors
Option 1: Use Power Virtual Agent for chatbot flows. Option 2: Use connectors (Slack-like automation). Build flow triggered by Teams message or mention. Route messages to appropriate handlers.
-
3Set up adaptive cards for interactive experiences
Design adaptive card templates in Power Automate: approval cards, form cards, data display cards. Send cards to Teams channels when events trigger (e.g., 'New help desk ticket approved').
-
4Implement notification routing
Create flows that route notifications to Teams channels based on priority/category: 'Urgent' → @channel mention; 'Info' → no mention. Aggregate notifications to reduce noise.
-
5Build Teams-to-backend connectors
Connect Teams messages/approvals to backend systems: approve in Teams → update SharePoint list → trigger invoice process. Use HTTP connectors or Dataverse for data sync.
-
6Test bot and connector with pilot users
Launch bot/automation to test team. Gather feedback on card design, messaging clarity, workflow logic. Iterate before org-wide rollout to prevent user frustration.
All five automations in this guide are built with Power Automate (make.powerautomate.com). They require:
LicenceMicrosoft 365 Business Standard, Premium, or any E plan — Power Automate is included
PermissionsOwner or Member in the relevant Teams channel; Planner access for flows that create tasks
Connectors usedMicrosoft Teams, Microsoft Planner, Outlook (for some flows) — all standard connectors, no premium licence required
Building tip: Create and test each flow using a test Teams team and test Planner plan before enabling it in a production team. Power Automate's built-in "Test" button lets you run the flow manually with a sample trigger to verify each step before going live.
Automation 1: Meeting Action Items → Planner Tasks
1
Meeting Action Items to Planner
After a Teams meeting ends, the organiser posts action items in the meeting chat using a simple format (e.g., "ACTION: @Person — Task description by DD/MM"). This flow detects those messages, parses the action items, creates a Planner task for each one with the right assignee and due date, and posts a confirmation card back to the chat.
- Trigger: "When a new message is posted in a channel" (Microsoft Teams connector) — use keyword filter "ACTION:"
- Parse: Use "Compose" and string functions to extract the assignee (@mention), task text, and due date from the message body
- Create task: "Create a task" (Microsoft Planner) — Title = extracted task text, Assigned to = resolved user ID, Due date = extracted date
- Confirm: "Post message in chat or channel" (Teams) — send a card confirming the task was created with a link to Planner
This flow eliminates the "who was going to do that?" problem that follows most meetings. Action items are captured immediately in Planner, assignees get a notification, and nothing falls through the cracks between the meeting and the next standup.
Automation 2: Adaptive Card Approvals in Teams
2
In-Teams Adaptive Card Approval Flow
Instead of sending approval requests to email (where they get buried), this flow sends rich Adaptive Cards directly to the approver's Teams chat. The card shows all relevant request details, and the approver clicks Approve or Reject without leaving Teams. The decision is recorded in SharePoint and the requester is notified instantly.
- Trigger: "When an item is created" (SharePoint connector) — triggered when a new item is added to an Approvals SharePoint list
- Get approver: Look up the approver from the SharePoint item's Approver column (resolved to an email address)
- Send card: "Post an Adaptive Card and wait for response" (Teams connector) — design the card in the Adaptive Card designer with request details and Approve/Reject buttons
- Update SharePoint: "Update item" (SharePoint) — set Status to Approved or Rejected based on the card response; record approver comments
- Notify requester: "Post message in chat" (Teams) — send a direct message to the original requester with the decision
What makes Adaptive Cards powerful
Adaptive Cards are JSON-defined UI cards that render natively inside Teams. Unlike plain text messages, they can include structured layouts with labelled fields, images, expandable sections, and interactive buttons that trigger Power Automate actions. The Adaptive Card Designer at adaptivecards.io lets you build cards visually and preview them in Teams before using the JSON in Power Automate.
📄 Microsoft Teams cards reference — learn.microsoft.comAutomation 3: New Team Member Welcome Flow
3
Automated New Member Welcome
When a new member joins a Teams team, this flow automatically sends them a personalised welcome message in the General channel, sends them a direct message with an onboarding checklist, adds them to the relevant Planner plan, and optionally creates a SharePoint onboarding checklist item for HR to track progress.
- Trigger: "When a team member is added" (Microsoft Teams connector) — fires when any new member joins the specified team
- Get user details: "Get user profile" (Office 365 Users) — retrieve display name, job title, and department to personalise the message
- Post welcome card: "Post an Adaptive Card to a Teams channel" — welcome card with the new member's name, photo, and links to key team resources (SharePoint site, shared OneNote, team agreements)
- Direct message: "Post a message in a chat" (Teams) — send the new member a private onboarding checklist as an Adaptive Card with checkboxes they can tick off
- Add to Planner: "Add a member to a plan" (Planner) — adds the user to the team's Planner plan so their task assignments work correctly from day one
Pro tip: Customise the welcome card by team. A welcome to the Engineering team should link to the dev wiki and deployment process. A welcome to Sales should link to the CRM guide and territory map. Store team-specific onboarding content in SharePoint and have the flow look it up by team ID.
Automation 4: Keyword Alert Monitor
4
Teams Channel Keyword Monitor
Monitors one or more Teams channels for specific keywords — competitor names, critical client mentions, escalation phrases like "urgent" or "down", or regulatory terms. When a keyword is detected, the flow immediately notifies a specific person or posts to an escalation channel, ensuring nothing important is missed in high-volume channels.
- Trigger: "When a new message is posted in a channel" (Teams) — set for each monitored channel (use separate flows per channel for reliability)
- Check keyword: "Condition" action — use
contains(triggerBody()?['body/content'], 'keyword')— chain multiple conditions with OR for multiple keywords - Notify: If condition is true, "Post message in chat or channel" (Teams) — post to an alerts channel with the original message link, sender name, and matched keyword highlighted
- Log: Optional — "Add a row" (SharePoint) to keep a searchable log of all keyword matches with timestamps for compliance purposes
Common use cases: a sales team monitoring for their competitor's name across all customer-facing channels; a support team watching for "system down" or "critical" in any project channel; a compliance team logging all messages mentioning specific regulatory terms in finance or healthcare environments.
Automation 5: Weekly Team Digest Card
5
Monday Morning Team Digest
Every Monday morning, this scheduled flow posts a rich Adaptive Card digest to the team's General channel, showing: open Planner tasks due this week (with assignees), any SharePoint pages published last week, upcoming calendar events for the team, and a "last week's wins" prompt that rotates a different team member each week to share a highlight.
- Trigger: "Recurrence" (Schedule) — set to every Monday at 8:30am in the team's timezone
- Get Planner tasks: "List tasks" (Planner) — filter for tasks due in the next 7 days in the team's plan; format as a bulleted list grouped by assignee
- Get SharePoint news: Use the SharePoint REST API with "Send an HTTP request to SharePoint" — query the team site's news for items modified in the past 7 days
- Get calendar events: "Get calendar view of events" (Office 365 Outlook) — retrieve shared calendar events for the current week
- Assemble and post: "Post an Adaptive Card to a Teams channel" — combine all data into a structured digest card with sections for Tasks, News, Events, and the rotating wins prompt
The weekly digest replaces the Monday morning status meeting that most teams dread. Team members arrive informed, with their tasks visible and the week's events clear — before the first standup begins. The "wins" prompt builds team culture by ensuring positive outcomes are shared systematically, not just when someone remembers.
Tips for Building Reliable Teams Automations
- Use service accounts for flow ownership: Flows owned by individual employees break when those employees leave. Create a shared service account (e.g., [email protected]) as the flow owner and connection owner.
- Add error handling to every flow: Use the "Configure run after" setting on critical steps to add a failure branch — at minimum, send an email to the IT team when a flow fails.
- Test with real data, not just the trigger: Power Automate's "Test" button is good for trigger validation, but test the full flow end-to-end with real Teams messages or real SharePoint items before turning on for production.
- Monitor flow run history: Check the flow's run history weekly for the first month. Failed runs are often silent — the error only appears in the run history, not in Teams.
- Throttle notification flows: Keyword alert flows can become noisy if a keyword appears frequently. Add a "Delay" action or a SharePoint de-duplication check to avoid sending the same alert multiple times in quick succession.
Need a custom Teams automation?
OceanCloud can design and build Power Automate flows tailored to your Teams setup — from simple notifications to complex multi-step approval workflows with Adaptive Cards and SharePoint integration.
Discuss Your Automation NeedsFrequently Asked Questions
Power Automate can post adaptive card messages to channels, create Planner tasks from meeting action items, send approval requests inside Teams, trigger welcome messages for new members, monitor keywords in conversations, and send weekly digest cards — all without any custom development.
Most Teams automations use standard connectors (Teams, Planner, SharePoint, Outlook) which are included in Microsoft 365 business licences.
Premium connectors like HTTP requests or third-party SaaS integrations require a Power Automate Premium (formerly Per-User) plan.
Use the 'Post adaptive card in a chat or channel' action in the Teams connector.
You provide the team and channel, then paste in your adaptive card JSON. Use the Adaptive Cards designer at adaptivecards.io to build the card visually, then copy the JSON into Power Automate.
Yes.
Use the 'When a new channel message is added' trigger, then add a Condition action that checks if the message body contains your keyword. Because Teams stores message content as HTML, use a 'contains' check on the body/content field, not an exact match.
Use the 'When a Teams meeting ends' trigger (requires Teams Premium or Meeting Recording connector), then parse the meeting transcript or action items with an AI action, and create Planner tasks via the Planner connector.
For simpler setups without Teams Premium, use a post-meeting form or an approval step that extracts actions manually.