Automatic Deadline Reminders from Lists and Calendars

A deadline that only exists in a list or calendar helps no one as long as nobody actively checks it. Bid deadlines, contract terminations, project milestones, or recurring reports get lost in daily business when the reminder depends on chance, on whether someone happens to have time to check the list. With Power Automate, a digital worker takes over this job, sending a message in Teams or an email in good time straight from a SharePoint list or a calendar, without you having to remember it yourself.

This article shows two ways to do this, both achievable with official Power Automate features: the ready-made reminder flow that SharePoint provides out of the box, and your own scheduled cloud flow with which you check deadlines from a list and report them via Teams or email. You stay in control of who gets which reminder and when, and you don't need to write a single line of code.

The quick way: the ready-made reminder flow for SharePoint lists

If your deadlines are already maintained in a list from Microsoft Lists or a SharePoint library, you don't need to build your own flow at all. SharePoint comes with a ready-made template designed exactly for this case: a personal email reminder, a number of days before a date in the list that you define yourself.

The prerequisite is a list or library with at least one DateTime column in the current view, such as "Due date" or "Deadline". After that, just a few clicks are needed: open the list, choose Automate > Set a reminder and then the matching date column. Next, you give the flow a name and specify how many days in advance the reminder should arrive. Once the flow is created, it runs in the background like any other flow and can be edited at any time via Power Automate to change the lead time in days or add further actions, for example. Microsoft documents the exact steps in the article on the reminder flow for SharePoint lists. Important to know: this feature is not available in GCC, GCC High, DOD, and other sovereign clouds.

For individual, clearly defined deadline lists, this is the fastest way. But as soon as you want to combine several conditions, notify via Teams instead of email, or map several escalation levels, the ready-made template reaches its limits and a custom flow is worthwhile.

Full control: your own scheduled cloud flow

For anything that goes beyond a simple reminder, you build a scheduled cloud flow yourself. This flow type starts at fixed times or intervals, regardless of whether anything changes in the list at that moment, which makes it ideal for a daily check of all open deadlines.

When setting it up, you specify in the Starting field the date and time of the first run, and in the Repeat every field the frequency, for example daily at seven in the morning. Pay deliberate attention to the time zone: Power Automate lets you choose between your local time zone and UTC, and a wrongly chosen time zone is one of the most common reasons a reminder arrives at the wrong time or on the wrong day. All the details on the start time format, frequency, and the differences between the new and classic designer can be found in the article Run a scheduled cloud flow.

Within this scheduled flow, you then read out the list containing your deadlines, step through each entry with a loop, and compare the due date with today's date. How to formulate such date comparisons with functions like addDays and formatDateTime is explained step by step in the introduction to Power Automate expressions step by step.

Step by step: checking and reporting deadlines from a list

A typical deadline flow always follows the same basic pattern, regardless of whether the end result is an email or a Teams message:

• Trigger: a scheduled cloud flow that starts once a day.
• Get items: the action retrieves all entries from the deadline list, if needed already filtered for open or not yet completed deadlines.
• Apply to each: a loop goes through each list entry individually.
• Check condition: a comparison determines whether the due date falls within the desired lead time, for example three days before the deadline.
• Notify: if the condition is met, the flow sends an email or posts a message in Teams, each time with the dynamic values from the list entry, such as title, due date, and person responsible.

This pattern can be extended as needed, for example with a second condition for a sharper reminder on the due date itself, or with an escalation to a manager if a deadline has already passed.

Delivering the reminder where your team is actually looking: Teams instead of just email

Email inboxes are often overcrowded, whereas Teams channels are opened much more actively in everyday work. For the notification itself, you use the Post message in a chat or channel action from the Teams connector.

In doing so, you decide via the option Post as whether the message appears as a neutral flow bot or as the user signed in to Power Automate, and via Post in whether it goes to a channel, an existing group chat, or directly as a chat with the flow bot to a single person. For deadline reminders to a single responsible person, a direct message is usually the right choice; for team-wide deadlines, a channel post. If you also want to draw someone's attention specifically, the action Get @mention token for a user retrieves a mention that you insert into the message text. All variants with the respective configuration steps can be found in the article Send a message in Teams with Power Automate. You should know two limitations: the dropdown list shows only the fifty most recently active named group chats, and sending messages to private channels is currently not supported.

There's nothing stopping you from using both channels at the same time: a Teams message for quick visibility in everyday work, plus an email action in parallel for anyone who prefers checking their inbox or doesn't receive Teams notifications while on the go.

Practical tips for reliable deadline reminders

• Set the time zone consistently: Deliberately choose your local time zone for the scheduled flow, otherwise the sending time will shift with daylight saving changes or for colleagues in other regions.
• Avoid duplicate reminders: Mark entries that have already been reminded, for example via an additional column "Reminder sent", so the flow doesn't send the same message again on every run.
• Plan for multiple escalation levels: An early, friendly reminder a week beforehand and a more urgent one on the due date itself reach different people with different levels of urgency.
• Don't forget error handling: Regularly check the flow's run history in Power Automate, so that a failed run doesn't silently let an entire deadline slip through unnoticed.
• Keep an eye on permissions: The flow runs with the access rights of the person who created and connected it. If that person leaves the company, the flow should be transferred to a co-owner in good time.

If you'd rather not click together such a deadline reminder yourself on the side, but want it set up cleanly from the start, including escalation levels and error handling, the Power Automate consulting from NordFlux provides a contact who sets up the flow together with you for production use.

Frequently asked questions

Can I also send reminders from an Outlook calendar instead of a list?

Yes. Instead of the action that retrieves entries from a SharePoint list, you use an action that retrieves calendar events from Outlook, and compare their start or due time with the current date in exactly the same way as with a list. The rest of the setup, consisting of a scheduled trigger, loop, condition, and notification, stays identical.

How do I prevent the same deadline from being reported multiple times?

The most reliable approach is an additional column in the list that the flow sets to "reminded" after sending. The condition in the flow then additionally checks whether this column is still empty before a new message is sent. Without this marker, the flow would trigger again on every daily run for as long as the deadline lies within the defined lead-time window.

Can the reminder be sent via Teams and email at the same time?

Yes, without restriction. Within the same flow, both the action for sending an email and the action for posting a Teams message can be inserted one after another following the condition, so that both channels are served simultaneously on every match.

What does such a deadline flow cost in Power Automate?

This depends on your existing Microsoft 365 licensing. Many Business and Enterprise plans already include a basic allowance of Power Automate runs for flows within Microsoft 365, so no additional license is usually needed for simple deadline flows with SharePoint, Outlook, and Teams. For very high volumes or premium connectors, it's worth checking Microsoft's current licensing overview.

Can I set up several reminder stages, for example seven days and one day beforehand?

Yes, to do this you add two separate conditions with different lead times to the flow, for example one for seven days and one for one day before the deadline, and link each one to its own appropriately worded message. This way, responsible people first get a calm advance notice and a noticeably more urgent reminder shortly before the deadline expires.