Notion Wiki to SharePoint Mirror

Overview

This flow mirrors a Notion knowledge/wiki database into a SharePoint document library so Notion-authored knowledge is covered by Microsoft 365 search, retention, and eDiscovery. On a daily schedule it reads every page in the wiki database, converts each page's blocks to a branded HTML document, and writes it to SharePoint. A Dataverse ledger table tracks each mirrored page (Notion page id, last-edited timestamp, SharePoint item id, status) to provide change detection (only re-mirror pages that changed), de-duplication, and archive handling - when a page disappears from Notion the flow deletes its SharePoint mirror and marks the ledger row Archived. A summary email is sent after each run.

Why it matters: Knowledge authored in Notion sits outside Microsoft governance. A scheduled, metadata-preserving mirror gives compliance and search teams a governed SharePoint copy without forcing authors off Notion.

Built and shipped Off (demo). Going live requires only authorizing the four connections, setting the environment variable values, and turning the flow On.

Use Case

A team authors documentation in a Notion wiki, but the organization requires that knowledge be searchable and retained in SharePoint/Microsoft 365. They want an automatic mirror that keeps content and metadata in sync and cleans up removed pages, without manual copy-paste.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Notion	shared_notionip	Query_a_database Retrieve_block_children
SharePoint	shared_sharepointonline	CreateFile DeleteItem
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord UpdateRecord
Office 365 Outlook

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.

Cadence

Change the Recurrence frequency/interval (default Day/1) to mirror more or less often.

Selective mirror

Add a Filter array after Query Notion Wiki Database to mirror only pages with a given status/tag (e.g. Approved/Public).

Richer HTML

Extend Select Block Html to map more Notion block types (headings, lists, code) instead of paragraphs only.

Attachments

For embedded files, add a Notion file read + a second SharePoint CreateFile and relink in the HTML.

Retention labels

To apply a real Microsoft Purview label, add a SharePoint REST SetComplianceTag (or Graph) HTTP call after CreateFile; the connector has no label op.

Notify target

Point flowlibs_MirrorNotifyEmail at a distribution list, or swap the Outlook step for Teams.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@coalesce(items('Apply_to_each_Page')?['properties']?[variables('varTitleProperty')]?['title']?[0]?['plain_text'],'Untitled')

@coalesce(items('Apply_to_each_Page')?['properties']?[variables('varCategoryProperty')]?['select']?['name'],'')

@concat('<p>',coalesce(item()?[item()?['type']]?['rich_text'][0]?['plain_text'],''),'</p>')

or(equals(length(body('List_Ledger_Match')?['value']),0), not(equals(coalesce(first(body('List_Ledger_Match')?['value'])?['flowlibs_lastedited'],''), outputs('Compose_Last_Edited'))))

not(contains(variables('varActivePageIds'), items('Apply_to_each_Ledger')?['flowlibs_notionpageid']))

@{first(body('List_Ledger_Match')?['value'])?['flowlibs_notionwikimirrorlogid']}

Customize & download