Notion Content Calendar Publisher

Overview

This solution drives content publishing from a Notion editorial calendar into Microsoft 365. It is built as two cloud flows in one solution (CF-450):

1. FlowLibs - Notion Content Calendar Publisher — every 15 minutes, finds Notion pages that are Approved, whose Scheduled Date has arrived, and that have no Live URL yet; publishes each to a SharePoint content list, writes the live link + Published status back to the Notion page, and confirms in a Teams marketing channel. 2. FlowLibs - Content Calendar Weekly Readiness — every Monday 08:00, scans the same calendar for posts scheduled in the next N days that are not yet Approved, and posts a readiness summary to the Teams channel.

Why it matters: Marketing teams plan content in Notion but publishing is manual and easy to miss. Driving it from the approved-calendar state gives consistency, an approval trail, idempotent publishing, and one source of schedule truth — plus a forward-looking nudge for posts still missing assets.

> Built API-first. Both flows ship Off; going live requires only connection authorization and environment-variable configuration.

Use Case

A marketing team manages its content calendar in Notion and wants approved items published on schedule automatically, the live link captured back in Notion, confirmation in Teams, and weekly visibility on what is coming up but not ready.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Notion (Independent Publisher)	shared_notionip	Query_a_database
SharePoint	shared_sharepointonline	PostItem
Microsoft Teams	shared_teams	PostMessageToConversation

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.

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.

Notion property names (required schema)

The flows expect these properties on the calendar database: a Status select (Approved / Published), a Scheduled Date date, a Live URL url, and a Name title. Rename in the expressions if your database differs.

Polling cadence

Adjust the Every_15_Minutes recurrence for faster/slower publishing.

Readiness window

Change varReadinessWindowDays (default 7) in Flow 2 to widen/narrow the look-ahead.

Status labels

varApprovedStatus / varPublishedStatus are Initialize Variables so the gating labels can change without touching logic.

Publish target

Publish_Content writes only the Title column to keep the list schema-agnostic; add item/<column> mappings (Body, Channel, Author) once your SharePoint list columns exist.

Multi-channel

Fan Publish_Content out to LinkedIn / X via their connectors, or call a downstream social-publishing flow.

Approval gate

Require a Power Automate Approval before a page becomes Approved.

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.

@and(equals(item()?['properties']?['Status']?['select']?['name'], variables('varApprovedStatus')), and(lessOrEquals(coalesce(item()?['properties']?['Scheduled Date']?['date']?['start'], '9999-12-31'), utcNow()), empty(coalesce(item()?['properties']?['Live URL']?['url'], ''))))

@{concat(parameters('EnvVar_NotionApiBaseUrl'), '/v1/pages/', item()?['id'])}

{ "properties": { "Status": { "select": { "name": "Published" } }, "Live URL": { "url": "<SharePoint item link>" } } }

@{item()?['properties']?['Name']?['title']?[0]?['plain_text']}

Customize & download