Create LinkedIn posts and read member/organization info via the versioned Posts API.
About
LinkedIn ships in the w6w first-party pack. It declares 6 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.linkedin- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Social Media · Marketing
Overview
LinkedIn’s own API is narrow by design, and this app covers exactly what it allows: posting text or article updates, reading a post back by its id, deleting one, and reading basic profile or organization information for whoever is connected.
Posting as an organization — and reading the posts an organization has published — needs LinkedIn’s separate Community Management approval, which is why this app offers two connection methods rather than one: a default that works with any LinkedIn developer app for posting and reading as yourself, and a second for the organization-level access LinkedIn gates behind its own review. A workflow using the wrong one for an action gets LinkedIn’s own permission error rather than a silent failure.
Attaching an image or video to a post isn’t supported, because LinkedIn’s upload flow hands back a one-time, unpredictable address this app’s sandboxed network access can’t reach ahead of time — an article post can still carry a thumbnail if one has already been uploaded elsewhere. Post analytics sit behind a separate, harder-to-get advertising approval and aren’t included either.
Build with LinkedIn
Three routes to the same 6 actions. The Workflow tab is generated from LinkedIn's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create Post
create-post Publish a text or article post as yourself or as an organization you manage.
Delete Post
delete-post Delete a post by its URN. Safe to retry — LinkedIn's own delete is idempotent.
Get Current Member Profile
get-current-member-profile Fetch the authenticated member's OpenID Connect profile (id, name, email).
Get Organization
get-organization Fetch a company page's profile by its numeric id. Requires the Community Management auth method and an ADMINISTRATOR role on that page.
List Posts by Author
list-posts-by-author Find posts by a person or organization URN. Requires r_member_social (person, approved-partner only) or r_organization_social (organization, Community Management API).
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying LinkedIn's real ids.
{
"manifestVersion": "2",
"name": "linkedin-example",
"steps": [
{
"id": "create-post",
"uses": {
"app": "io.w6w.linkedin",
"action": "create-post",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"authorType": "<authorType>",
"authorId": "<authorId>",
"commentary": "<commentary>"
}
}
]
}Here are some of the things you can do
-
Create Post
performcreate-post -
Get Current Member Profile
readget-current-member-profile -
Get Organization
readget-organization -
Get Post
readget-post -
List Posts by Author
readlist-posts-by-author
+1 more action available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for LinkedIn, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to LinkedIn. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "create-post",
payload: {
authorType: "<value>",
authorId: "<value>",
commentary: "<value>",
// visibility: "<value>",
// contentType: "<value>",
// articleUrl: "<value>",
// articleTitle: "<value>",
// articleDescription: "<value>",
// articleThumbnailImageUrn: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action create-post --payload '{"authorType":"<value>","authorId":"<value>","commentary":"<value>"}'Give an AI agent LinkedIn — without giving it LinkedIn's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.linkedin#create-post",
"input": {
"authorType": "<authorType>",
"authorId": "<authorId>",
"commentary": "<commentary>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's LinkedIn connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
LinkedIn's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. LinkedIn itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
LinkedIn declares its own checks, so its health is a property of the app rather than something the host guesses at.
LinkedIn API status
Atlassian Statuspage rollup for www.linkedin-apistatus.com, LinkedIn's official API status page, with per-component detail. Unauthenticated and unsigned.