“Any update?” is an expensive habit when the answer is scattered across chat, spreadsheets and someone’s memory. A small operations team does not need an AI agent to chase every task. It needs a reliable action register and one short message showing what is overdue, who owns it and where to update the record.
This guide builds a weekday Teams digest from a SharePoint-backed Microsoft List using Power Automate. It is a reminder system, not an approval workflow: people still decide whether work is genuinely complete.
1. Check access and licensing first
You need SharePoint Online, access to Power Automate, a Teams entitlement and membership in a standard channel used by the intended audience. The flow’s SharePoint connection needs read access to the list; whoever builds its columns needs permission to manage the list. Contributors need editing access to update their actions. Do not grant tenant-wide administration for this task.
SharePoint and Teams are standard connectors. Microsoft’s September 2026 licensing documentation permits standard-connector cloud flows under Power Automate Free, but Free does not include flow sharing. For a maintained team flow with a co-owner, confirm an eligible seeded Microsoft/Office 365 entitlement or other qualifying licence. No Copilot, AI Builder or premium connector is required for this design. Premium additions change the licensing assessment.
Ask the administrator to confirm that environment policies permit both connectors and that the Teams Workflows app is allowed. Use a standard channel for this pilot: the current connector documentation says posting to private channels is unsupported. Source access and destination audience must match.
2. Make the list usable before automating it
Create a list on the relevant team’s SharePoint site, not a personal workspace. Keep these column names simple when first creating them: Title, Owner (single-person), DueAt (date and time), Status (Open, Blocked, Closed) and NextAction (short text). Require Owner and DueAt for actionable entries.
Agree what the deadline means. In this example, a task becomes overdue when its actual deadline passes—not merely because its calendar date is today. Set and verify the SharePoint site’s regional time zone for Kuala Lumpur. Avoid mixing date-only promises with precise timestamps.
3. Create the weekday schedule
In Power Automate, create a scheduled cloud flow, or a blank cloud flow with the Recurrence trigger. Set Frequency to Week, Interval to 1, Monday through Friday, hour 9 and minute 0. Select the UTC+08:00 Kuala Lumpur/Singapore time zone. Designer labels can vary; check the saved trigger configuration before enabling it.
A cloud flow runs in Microsoft’s service; this design does not need an office PC left on. The schedule’s time zone controls when the flow starts. Retrieved timestamps still need separate handling when displayed to readers.
4. Retrieve overdue items, not the first page
Add SharePoint Get items, selecting the site and list. In Filter Query, use this pattern, replacing the timestamp placeholder with the expression utcNow() inserted through the designer:
Status ne 'Closed' and DueAt ne null and DueAt le '<UTC timestamp>'
Keep the single quotes around the inserted value. Use the columns’ internal names if yours differ. Set Order By to DueAt asc. SharePoint stores date-time values in UTC, so compare to UTC here and convert only for presentation.
The default Get items response is limited to 100 items. Configure pagination and an appropriate threshold for the pilot, and check returned counts against the list. Do not set Top Count to ten before counting the backlog. Larger lists need indexed filter columns and a reviewed query strategy; pagination is not permission to ignore SharePoint’s list-view threshold.
5. Build one short message
Add a Condition: continue only when the returned value array contains items. For an action internally named Get_items, count them with length(body('Get_items')?['value']) and select the oldest ten with take(body('Get_items')?['value'],10). Use Select to shape those ten into Title, Owner display name, local deadline and NextAction; use Create HTML table on that result. For the deadline mapping, use convertTimeZone(item()?['DueAt'],'UTC','Singapore Standard Time','dd MMM yyyy HH:mm').
Add Teams Post a message in a chat or channel, choose Flow bot, Channel, then the exact team and channel. Include the snapshot date, total retrieved overdue count, the short table and a link to the overdue list view. State “showing oldest ten” where applicable. Keep sensitive notes out of the message: posting copies information into the channel and does not inherit the list’s item permissions.
6. Prove it works, then assign ownership
Test with an overdue Open item, overdue Closed item, future deadline, blank deadline and an item near midnight Malaysian time. Confirm only eligible records appear and an ordinary channel member can open the list link. Run a no-overdue test too; silence must not be confused with a failed flow.
Add a co-owner, document whose connections are used, and route failures to a named maintainer. Include a daily run key such as the local date in the message; log successful posting before manually rerunning a failed run. A Teams post and a log update are separate actions, so retries can still duplicate a message. Review run history before resubmitting.
Hypothetical example: A 30-person Malaysian consultancy tracks client-document follow-ups in one list. Each weekday, its operations channel receives the oldest overdue actions. Owners update the list, not the reminder thread. Closed items disappear from the next digest; blocked work stays visible until someone resolves it.
The payoff is a shared follow-up routine with a source of truth. Start with one low-risk list, one audience and one accountable owner.
For help planning practical Microsoft 365 automation, contact AXO Technologies.
