LinkedIn Approval-Gated Post Publishing

Overview

This flow adds governance and brand control to LinkedIn publishing. An employee submits a draft post as a row in a Dataverse table; the flow routes it through a comms/marketing approval, and only on approval publishes the article to the chosen personal profile or company page, then stamps the row Published and notifies the marketing Teams channel. Rejected posts are recorded and never published.

Why it matters: off-brand or unreviewed posts are a reputational risk. An approval gate ensures every LinkedIn post is reviewed before it goes live, with a full audit trail (approver outcome, comments, timestamps) kept in Dataverse.

Ships Off (Stopped).

Use Case

Employees draft LinkedIn posts but comms must approve before anything is published - especially to the company page. Each draft is a row in the Social Post table (commentary, article link/title/description, target, visibility, submitter). The flow handles review, publishing, logging, and notification automatically.

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.

Tiered approval

Add an exec-level approval for sensitive topics or company-page posts.

Edit loop

On rejection, route back to the submitter for revision instead of just logging.

Approve now, post later

Add a Delay or a scheduled companion flow keyed off Approved On.

Capture the post id

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

Submission channel

Swap the Dataverse trigger for a Microsoft Forms OnNewResponse or a Teams message trigger if drafts come from there.

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.

equals(outputs('Request_Comms_Approval')?['body/outcome'], 'Approve')

equals(toLower(coalesce(triggerOutputs()?['body/flowlibs_target'], '')), 'company')

if(empty(triggerOutputs()?['body/flowlibs_visibility']), variables('varDefaultVisibility'), triggerOutputs()?['body/flowlibs_visibility'])

first(outputs('Request_Comms_Approval')?['body/responses'])?['comments']

triggerOutputs()?['body/flowlibs_socialpostid']