LinkedIn Milestone and PR Announcement

Overview

This flow turns business milestones into timely, approved LinkedIn company-page announcements. When a new Milestone row is created in Dataverse - a closed deal, a product release, an award, or a new hire - the flow resolves the post's visibility, routes a quick approval to a configured reviewer, and on approval posts a branded article update to the LinkedIn company page, writes the outcome back to the milestone row, and cross-posts a heads-up to a marketing Teams channel. On rejection it marks the row and notifies Teams with the reviewer's comments.

Why it matters: great milestones often go unannounced because no one gets around to posting. Event-driven drafting plus a light approval gate makes public celebration consistent, accurate, and on-brand - with a governed record of what was approved and when.

Ships Off (demo).

Use Case

Marketing and Sales teams want notable business events automatically turned into reviewed LinkedIn posts, without manual drafting each time. A simple Dataverse table acts as the milestone intake: any system (CRM plugin, Power Apps form, another flow) can drop a row in, and this flow handles review, publishing, and team notification.

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.

Milestone intake

Point any source (CRM plugin, model-driven form, another flow) at the flowlibs_milestone table; populate commentary, article url/title/description, and milestone type.

Approver

Change flowlibs_ApproverEmail, or swap the Basic approval for an approver-group / first-to-respond pattern.

Default visibility

Edit Initialize Default Visibility (Public / Logged in members only). Per-row override via flowlibs_visibility.

Consent gate

Add a condition that holds New Hire types until a consent flag column is set.

Channels

Repoint flowlibs_TeamsGroupId / flowlibs_TeamsChannelId to the right marketing channel.

Personal vs company

To post to a personal profile instead, swap PostCompanyUpdateV2 for PostUpdateV2 and drop body/author.

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('urn:li:organization:', parameters('EnvVar_CompanyPageId'))

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

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

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

triggerOutputs()?['body/flowlibs_milestoneid']