LinkedIn Scheduled Content Calendar Publisher

Overview

This flow turns a Dataverse-backed content calendar into automated LinkedIn publishing. On an hourly schedule it reads the next due entry from the calendar table, posts it to LinkedIn as an article - on a personal profile or a company page depending on the row - marks the entry Published, and notifies the marketing Teams channel.

Why it matters: keeping a steady LinkedIn cadence by hand is error-prone. A calendar-driven publisher posts on time, every time, with no daily effort - and the calendar stays the single source of truth.

Ships Off (demo).

Use Case

A marketing/operations team plans LinkedIn posts in advance. Each planned post is a row in the content-calendar table with its commentary, the article it links to, the target (personal or company), the visibility, and a scheduled date/time. The flow publishes each row at the right time and reports back to the team channel.

Flow Architecture

Environment Variables

Connectors & Connections

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.

Cadence

Change the recurrence interval (e.g. every 30 minutes, or weekday mornings only).

Approval gate

Insert an Approvals step before publishing high-stakes posts.

Image/media posts

Extend the table and content object to support image or document shares instead of article links.

Capture the post id

Parse the LinkedIn action output into flowlibs_posturn for later analytics or deletion.

Multi-channel

Add parallel branches to cross-post to other networks from the same calendar row.

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_status eq ''Scheduled'' and flowlibs_scheduleddate le ', variables('varNowUtc'))

first(outputs('List_Due_Calendar_Entries')?['body/value'])

if(empty(outputs('Get_Next_Due_Entry')?['flowlibs_visibility']), variables('varDefaultVisibility'), outputs('Get_Next_Due_Entry')?['flowlibs_visibility'])

equals(toLower(coalesce(outputs('Get_Next_Due_Entry')?['flowlibs_target'], '')), 'company')