Automatic Monday Report: The Weekly Report via Recurrence Trigger

Every Monday morning the same routine: gather numbers from a list or table, copy them into an email, and send it to the team before the weekly meeting begins. On its own, this might take ten minutes, but it's ten minutes that come up every single week, usually right when the first deadline of the week is already looming. And as soon as someone is sick or on vacation, the report is missing entirely because no one steps in to cover it.

That's exactly what the scheduled cloud flow in Power Automate is made for. Instead of a person having to remember the report every Monday, a recurrence trigger takes over the reminder itself and kicks off the entire chain of data retrieval, preparation, and delivery on its own. This article shows step by step how such a Monday report is built, what you need to watch out for when scheduling it, and how to bring the collected data cleanly into an email. As digital employees, we at NordFlux build such recurring flows regularly, and you retain full control over the schedule, content, and recipients at all times.

The Scheduled Cloud Flow as a Starting Point

Power Automate distinguishes between automated, instant, and scheduled cloud flows. For a report that should run on its own every week without any external trigger, the scheduled cloud flow is the right choice. According to the documentation on running a cloud flow on a schedule you first define, when creating it, when the flow should start (Starting) and at what interval it repeats (Repeat every). These two settings automatically generate the Recurrence trigger in the background, which you then refine further in the designer.

You can either have Copilot generate the flow from a natural-language description or build it from scratch without Copilot. For a Monday report, the same core applies in both cases: the recurrence trigger as the first step, followed by the actions that fetch, prepare, and send the report data.

Setting the Schedule Precisely for Monday Morning

For the report to really run only on Monday and only at the desired time, you need the advanced options of the recurrence trigger. According to the documentation, you select Frequency set to Week and then configure three fields:

• On these days: here you select only Monday, even though the dropdown would allow multiple weekdays at once.
• At these hours: the hour or hours at which the flow should start, for example 7 for 7 a.m.
• At these minutes: the minute within that hour, comma-separated if several values are needed.

Additionally, in the field Time zone you define whether the start time refers to a local time zone or to UTC, and you enter the Start time in the format YYYY-MM-DDTHH:MM:SSZ. If you don't select a time zone, according to the documentation the start time must end with the letter Z, since this denotes UTC time. This might sound like a minor detail at first, but it decides whether your report actually arrives at 7 a.m. your local time or is suddenly shifted by an hour as soon as daylight saving time changes. Anyone who sets the time zone explicitly, instead of relying on UTC, avoids this hassle from the start.

A Newsletter Flow as a Blueprint for the Weekly Report

A good way to get a clear picture of the structure of such a flow is the official tutorial on getting started with cloud flows. There you build a monthly newsletter flow that consists of exactly two building blocks: the Recurrence trigger and the action Send an email (V2) from the Microsoft 365 Outlook connector. For the Monday report, you take over this basic structure almost unchanged, but change the frequency from month to week and replace the static newsletter text with dynamically assembled report data.

That last point is precisely the real difference between a simple reminder flow and an actual report: the email shouldn't contain the same text every week, but rather the current figures from a list, table, or calendar of the past week.

Collecting Weekly Data and Bringing It into the Email as a Table

For the actual report data, Power Automate has an established pattern, which the documentation describes under the term daily digest email with a table, and which can be applied one-to-one to a weekly report. According to the flows for popular email scenarios this happens in three steps:

• With the action Data Operation: Select you bring the raw data, for example from a SharePoint list or an Excel table, into the shape that should later appear in the email, including your own column names.
• The action Data Operation: Create HTML table then converts this array into a finished HTML table, complete with a header row.
• In the action Send an email (V2) you insert the output of the HTML table directly into the body text.

One detail that is easily overlooked in practice: according to the data operations in Power Automate you need to enable the option IsHtml in the email action, so that the table appears as an actual table and not as raw HTML code in the inbox. Without this one checkbox, the whole report suddenly looks like broken source code instead of a clean overview on Monday morning.

Practical Tips for a Reliable Monday Report

• Test manually first, then leave it to the schedule. Trigger the flow once by hand before relying on Monday morning, so that formatting errors in the table don't show up right in front of the whole team.
• Fixed hours and minutes instead of a vague repetition. If you enter concrete values for hours and minutes, the flow starts reliably at the same time instead of gradually drifting.
• Maintain the recipient list centrally. Enter multiple addresses in the To field or distribute the report via a distribution list, so you don't have to touch the flow itself every time the team changes.
• Catch empty weeks. Build in a condition before sending that checks whether any data is present at all, so no one interprets an empty table as a report.

When several such recurring reports come together in a company, each with its own schedule, its own data source, and its own recipients, it's worth taking a structured look at the entire automation landscape. At NordFlux's Power Automate consulting we help build such flows cleanly and keep them maintainable in the long run, instead of every report becoming its own little island.

Frequently Asked Questions

Does the recurrence trigger start immediately when I save the flow?

Without an explicitly set start time, the first execution can happen right when you save. If, on the other hand, you enter a concrete start time in the Start time field, the flow waits until that point and then follows the configured weekly repetition.

Do I need to specify hours and minutes separately, or is the start time alone enough?

For a weekly report, it's recommended to set the fields On these days, At these hours, and At these minutes in addition to the start time. With just a simple start time, the actual execution time can easily drift over several weeks.

Can I send the Monday report to several people at once?

Yes. In the To field of the Send an email (V2) action, you can enter multiple addresses, either individually or as an existing distribution list. This is especially handy when the recipient list changes over time and you don't want to touch the flow itself.

What happens if the underlying list or table is empty in a given week?

Without an additional check, the flow simply sends an email with an empty table as usual, which quickly looks confusing. A condition before the send action that checks the number of returned rows prevents this and can instead trigger a short notice email if needed.

How do I make sure the HTML table is actually displayed as a table in Outlook?

For that, the option IsHtml must be enabled in the Send an email (V2) action. If this checkbox is missing, the email shows the raw HTML code of the table as text instead of displaying it.