LinkedIn Company Page Post Scheduler

Overview

This solution publishes approved marketing content to a company LinkedIn page from a governed content calendar, then keeps the team informed. It is built as two cloud flows in one solution, both Off (demo) and fully wired so going live needs only connection authorization + environment-variable values.

A 15-minute publisher flow finds approved, due posts and publishes each to the LinkedIn company page, records the live post identifier back onto the calendar row, and confirms in a marketing Teams channel. A weekly readiness reminder flow scans upcoming approved posts that still lack assets and nudges the team in Teams.

Why it matters: Manual social posting is easy to forget and hard to govern. Driving LinkedIn from an approved calendar gives consistency, an approval trail, idempotent publishing (a post is never sent twice), and one place to manage the schedule.

> Build note — content calendar store. The original idea named a *SharePoint* content calendar. SharePoint list provisioning over REST is CORS-blocked from the maker origin in this tenant, so the content calendar is implemented as a Dataverse table (flowlibs_linkedinpostschedule) created inside this solution. This keeps the solution self-contained and tenant-portable, and is the documented FlowLibs substitution. To use a real SharePoint list instead, swap the Dataverse List records/Update a row actions for SharePoint Get items/Update item and repoint the calendar env var.

Use Case

A marketing team plans LinkedIn content in a calendar and wants approved posts auto-published on schedule, with the live link captured and the team notified — a clean, low-complexity, governed automation. A weekly reminder flags posts that are approved but still missing creative assets before their slot arrives.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
LinkedIn V2	shared_linkedinv2	PostCompanyUpdateV2
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords UpdateRecord
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.

Text-only posts

Leave flowlibs_articleurl empty and the post publishes as commentary only (drop the content/article/* parameters for a pure text share).

Per-row visibility

Add a visibility column to the table and bind body/visibility to it instead of the default env var.

Media

Attach an image/document (e.g. from SharePoint/OneDrive) to the LinkedIn post.

Multi-network

Fan the same approved row to X/Twitter or Facebook Pages with parallel actions.

Approval gate

Add an Approvals step that flips flowlibs_approvalstatus to Approved before a post is eligible.

Real SharePoint calendar

Swap the Dataverse actions for SharePoint Get items/Update item against a list with matching columns.

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.

@concat('flowlibs_approvalstatus eq ''Approved'' and flowlibs_posturl eq null and flowlibs_scheduledtime le ', utcNow())

@concat('flowlibs_posturl eq null and flowlibs_assetsready ne ''Yes'' and flowlibs_scheduledtime ge ', utcNow(), ' and flowlibs_scheduledtime le ', addDays(utcNow(), int(variables('varLookaheadDays'))))

@coalesce(body('Publish_To_LinkedIn')?['id'], body('Publish_To_LinkedIn')?['updateUrn'], body('Publish_To_LinkedIn')?['activity'], 'published')

@length(outputs('Get_Upcoming_Unready_Posts')?['body/value'])

Customize & download