LinkedIn

LinkedIn

This connector posts to LinkedIn as the member whose access token you paste, and reads that member's basic profile. Posts and images go through LinkedIn's versioned API at https://api.linkedin.com/rest with the header LinkedIn-Version: 202609; the profile comes from the OpenID Connect endpoint https://api.linkedin.com/v2/userinfo, which is not versioned.

What LinkedIn allows. LinkedIn's API is tightly gated. Without a review by LinkedIn an app gets two self-serve products: Sign In with LinkedIn using OpenID Connect (scopes openid, profile, email) and Share on LinkedIn (scope w_member_social: create and delete the member's own posts, upload images). Reading posts (r_member_social), posting for a company page (w_organization_social), and searching people or connections all need LinkedIn's approval of the app for the Community Management API. A token without those scopes cannot reach them, whatever the connector does.

Setup.

1. Create an app at https://www.linkedin.com/developers/apps. LinkedIn asks you to link it to a company page.
2. On the app's Products tab, add Sign In with LinkedIn using OpenID Connect and Share on LinkedIn.
3. Open https://www.linkedin.com/developers/tools/oauth, pick the app, tick openid, profile, email and w_member_social, and generate a token, signed in as the member you want to post as.
4. Paste the token into LINKEDIN_ACCESS_TOKEN and install. Tokens last 60 days; then generate a new one and update the variable.

Posting.

1. Call linkedin_userinfo. Its sub is the member id; the author URN is urn:li:person:<sub>.
2. Call linkedin_create_post with that author and the text in commentary. Visibility defaults to PUBLIC (or CONNECTIONS for the member's network only); the post goes to the main feed and is published at once, LinkedIn has no drafts here. LinkedIn answers 201 with an empty body: the new post's URN (urn:li:share:... or urn:li:ugcPost:...) is in the x-restli-id response header, which the tool returns with the result.
3. linkedin_delete_post takes that URN as it is, for example urn:li:share:7123456789012345678; the connector encodes it for the address. Deleting is idempotent.

Images. linkedin_register_image_upload with {owner: 'urn:li:person:<sub>'} returns an uploadUrl and an image URN (urn:li:image:...). The file itself has to be sent to uploadUrl with an HTTP PUT outside this connector. Then create the post with content: {media: {id: '<image URN>'}}.

Links. LinkedIn does not fetch a preview from the address, so a link post needs the details itself: content: {article: {source: '<URL>', title: '<title>', description: '<optional>'}}, with an uploaded image URN as thumbnail if you want a picture.

Reading a post. linkedin_get_post needs r_member_social, which LinkedIn grants to approved apps only. With the two self-serve products it answers 403, even for the member's own posts.

Errors. 401: the token expired or was revoked; generate a new one. 403 ACCESS_DENIED: the token lacks the scope for that call (see above). 400 MISSING_FIELD or INVALID_URN_TYPE: check that author is urn:li:person:<sub> and that commentary is not empty. 426 or a version error: LinkedIn retired the LinkedIn-Version the tools send (each version is supported for at least a year); update the connector from the catalog. 429: the daily limit per member and app; try again later.