هذه الصفحة متاحة حاليًا بالإنجليزية فقط.

Importing the notification flows

AlertSentinel's web part records who wants to be notified about what. Three Power Automate flows do the notifying. They run in your own tenant, under your own connections — which is why you import them rather than us running them for you.

What the flows do

Three flows cover every site in your tenant. They find your subscriptions by searching for the AlertSentinel_Subscriptions lists the web part creates, so you do not add a flow per site.

  • Immediate Notification — checks every 5 minutes and sends alerts for new and changed items.
  • Daily Digest — one message a day, at 07:00 UTC, collecting that day's activity.
  • Weekly Digest — the same digest batched weekly, Monday at 08:00 UTC.

All three use Standard connectors only — SharePoint, Office 365 Outlook and Microsoft Teams. No premium Power Automate licensing is required.

Before you start

  1. Install AlertSentinel and add the web part to at least one site, so an AlertSentinel_Subscriptions list exists. See Getting started.
  2. Sign in to make.powerautomate.com with an account that can create flows.
  3. Download the three packages from your customer portal.

Use one service account, not your own

The flows send notifications on behalf of whoever owns the connections. Using a dedicated account means alerts keep working when people change roles or leave.

Import each package

Repeat this for all three .zip files.

  1. In Power Automate, go to My flows → Import → Import Package (Legacy).
  2. Upload one .zip and wait for it to be inspected.
  3. Under Review Package Content, the flow itself is set to Create as new. Leave it.
  4. Under Related resources, each of the three connections shows Select during import. Choose or create your connection for SharePoint, Office 365 Outlook and Microsoft Teams. The import will not proceed until all three are set.
  5. Select Import. You should see "All package resources were successfully imported."

Set your SharePoint URL

This step is required, and it is the one that catches people out. Each flow ships with a deliberately invalid placeholder address so it cannot quietly point somewhere wrong.

  1. Open the imported flow and select Edit.
  2. Near the top of the flow, find the Initialize variable step whose value is https://YOUR-TENANT.sharepoint.com/. Go by that value, not by position or name: it is the very first step in the Daily Digest but the second in the other two, and it is named Sharepoint_Url in two flows and Sharepoint_URL in the Weekly Digest.
  3. Replace that value with your own SharePoint root address — for example https://contoso.sharepoint.com/. Keep the trailing slash.
  4. Save, then turn the flow on.

If you skip this, nothing happens — and nothing tells you

The flow will not show an error message or email anyone. Its own error logging uses the same address, so that fails too, and the error log stays empty. The only visible sign is a failed run in the flow's run history. After the first cycle, open the flow and check there before assuming AlertSentinel is not working.

Confirm it works

  1. Create an alert on a list you can edit, with frequency Immediate.
  2. Change an item in that list.
  3. Wait one 5-minute cycle.
  4. Open the Immediate Notification flow and check run history: the run should succeed, and you should receive the notification.

If nothing arrives

The flows locate your subscriptions through SharePoint search. A list created a few minutes ago has not been indexed yet, so the flow runs, finds nothing, and reports success. That looks identical to "nothing changed" and to "the product is broken", so check this before anything else.

Confirm the list is indexed by opening this URL in your browser, substituting your own tenant:

https://YOUR-TENANT.sharepoint.com/_api/search/query?querytext='Title:AlertSentinel_Subscriptions contentclass:STS_List'

If it returns no rows, the list is not indexed yet. SharePoint Online crawls continuously rather than on a published schedule, and Microsoft does not commit to a specific indexing time, so waiting is not a reliable plan. You can request indexing directly:

  1. Go to the AlertSentinel_Subscriptions list.
  2. Select Settings → List settings (you may need More list settings).
  3. Under General Settings, choose Advanced settings.
  4. Scroll to Reindex List and select it, then confirm. The content is reindexed during the next crawl.

Reindex the list, not the site

Microsoft warns that reindexing a whole site can put a heavy load on the search system. Only ever reindex the individual list.

Empty rows on monitored lists and libraries

When someone edits in grid view, SharePoint can commit a draft row with nothing filled in. If the item that results has an empty Title, a notification about it carries nothing useful.

Keeping Title as a required column on what you monitor avoids this. New lists require it by default, so there is usually nothing to change there — but check two cases:

  • Older lists where Title was later made optional.
  • Document libraries, where Title is optional by default and often unused. If you monitor a library, this is the case to look at.

Still stuck?

Email support@arrioph.com with the flow name and what its run history shows. That last part usually identifies the problem immediately.