Cloud FlowSharePoint & Cloud BridgingBeginner

SharePoint Page Published Notifier

When a SharePoint communication site page is published or updated, sends a notification to a Teams channel and distribution email list with a summary and link to the page.

SharePointMicrosoft TeamsOffice 365 Outlook

Unique name

flowLibsPagePublishedNotifierDemo

Publisher

FlowLibs (flowlibs)

Version

1.0.0.1

Components

4 env vars + 1 cloud flow

Request access

Provided as-is, without warranty of any kind. Review and test each pattern in a non-production environment before deploying it to live automations. See our Terms.

What it does

Overview

This flow watches a SharePoint communication site's Site Pages library for new or updated pages and, once a page is in a Published state, fans the announcement out to two channels: an adaptive card in a Teams channel and a formatted email to a communications distribution list. It is a lightweight, no-code-friendly way to make sure internal news posts on a SharePoint communication site are seen by people who do not regularly browse the site, without asking the author to send a separate announcement.

The flow runs on the SharePoint *When a file is created or modified (properties only)* trigger, then enriches the event with page metadata (title, author, modified date, URL), filters out drafts via a condition on the page layout status, and posts the resulting summary to Teams and Outlook. It is intentionally simple and designed to be a starting point — channel IDs, email recipients, and the card/email layout are all good candidates for promotion into environment variables before deployment.

Why you'd use it

Use Case

Internal Communications and Marketing teams use SharePoint communication sites to post news, but adoption suffers when employees don't visit the site regularly. This flow closes that gap by automatically broadcasting newly published pages to the channels people already monitor — a Teams channel for at-a-glance awareness and an email distribution list for people who prefer inbox-driven workflows. Because it triggers on the SharePoint pages library directly, communications authors don't have to change their workflow or remember to send a separate announcement; publishing the page IS the announcement.

The flow is ideal for teams that:

Internal Communications teams running a SharePoint communication site as the intranet hub
Marketing teams publishing campaign updates and product news on SharePoint
Organizations that want a single-source-of-truth for news (the SharePoint page) with automatic fan-out
Teams that need an audit-friendly notification pattern (Teams + email) without writing custom code

Step-by-step

Flow Architecture

When a SharePoint page is created or modified

When a file is created or modified (properties only) — SharePoint

Fires on the Site Pages library of a SharePoint communication site whenever a page's properties are created or updated. Configure the Site Address to point at the communication site and the Library Name to 'Site Pages'.

Get page details

Get file properties — SharePoint

Retrieves the full property set for the triggered page so the rest of the flow has the title, author, modified date, and page URL available as dynamic content.

If page is published

If condition

Checks the page layout status to ensure only fully Published pages trigger notifications (drafts and in-progress edits are ignored).

If yes (Published)2 actions run in series

Post adaptive card — Teams — Posts an adaptive card to the configured Teams channel (for example #company-news) containing the page title, author, thumbnail, description, and a 'Read More' button linking back to the SharePoint page.
Send an email (V2) — Outlook — Sends a formatted HTML email to the communications distribution list with subject 'New: <page title>' and a body containing the page summary, hero image, and a read link.

If no (Draft / other status)

Empty branch — no action. The flow exits silently for draft updates so editors aren't spammed mid-edit.

Solution config

Environment Variables

Schema name	Type	Default	Description
flowlibs_SharePointSiteUrl	String	https://your-tenant.sharepoint.com/sites/communications	The full URL of the SharePoint communication site whose Site Pages library should be watched.
flowlibs_TeamsChannelId	String	<configure>	The Teams channel that should receive the adaptive card. Use the channel's GUID (e.g. 19:xxxx@thread.tacv2). Find it via Teams > channel > Get link to channel.
flowlibs_TeamsGroupId	String	<configure>	The Microsoft 365 group ID that backs the Team containing the target channel.
flowlibs_EmailDistributionList	String	communications@yourcompany.com	Comma-separated list of email addresses (or a single distribution-list address) to notify when a page is published.

Auth dependencies

Connectors & Connections

Connector	API name	Actions used
SharePoint	shared_sharepointonline	OnNewOrModifiedFileProperties (trigger) GetFileProperties
Microsoft Teams	shared_teams	PostAdaptiveCardToChannel
Office 365 Outlook	shared_office365	SendEmailV2

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Tweaks & variations

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Promote channel, site, and recipients to environment variables: Move the SharePoint site URL, Teams channel/group IDs, and email recipient list into the provided flowlibs_* environment variables so the same managed solution can be deployed across Dev/Test/Prod without editing the flow.
Add a debounce / batch window: Insert a Delay action (or a scheduled aggregation pattern) before the notification so multiple rapid edits to the same page collapse into a single announcement instead of spamming the Teams channel.
Filter by page category or tag: Extend the condition to read a SharePoint page property (e.g. 'Audience' or 'Category') and only fan out to specific Teams channels / DLs that match — useful when the communication site serves multiple audiences.
Track click-through with UTM parameters: Append UTM query parameters (utm_source=teams, utm_campaign=page-publish) to the 'Read More' URL so engagement is measurable in your analytics tool.