LinkedIn Cross-Post

What it does

LinkedIn Cross-Post carries each new piece to your professional network as soon as it is live. When a post flips to published from any route (editor, bulk publish, REST API or scheduled run), the plugin first asks LinkedIn which member your token represents, then files a public article share under that member. The post text is the excerpt followed by the article link, or just the link when there is no excerpt, and the attached card carries the title and a short description. The link uses your verified custom domain, or your subdomain until one exists. A LinkedIn badge in the posts list reflects every attempt.

Who it's for

Consultants, founders and independent writers whose audience lives on LinkedIn and who publish under their own name. It is for people willing to set up a LinkedIn developer app and generate an access token with it, because VeloCMS does not run its own LinkedIn application and offers no sign-in button yet. Posts go to a personal profile, not to a company page.

How it works

1. 01

   In a LinkedIn developer app of your own, add the Sign In with LinkedIn using OpenID Connect product and the Share on LinkedIn product.

2. 02

   Generate an access token with the openid, profile and w_member_social scopes using LinkedIn's token generator, then paste it into the plugin and save.

3. 03

   Publish a post. The plugin responds to the switch into live and runs once for that article.

4. 04

   The plugin reads your member ID from LinkedIn's userinfo endpoint, then creates a public article share through the ugcPosts endpoint.

5. 05

   The outcome is saved with the article. Should LinkedIn refuse, the plugin panel displays a notice that names the missing scope or the expired token.

Settings you configure

Access Token

An OAuth 2.0 token carrying openid, profile and w_member_social. It is stored as ciphertext and not displayed again. Tokens lapse after 60 days and you renew them manually.

What it can access

From each published article the plugin takes the title, slug and excerpt, plus your site ID so it can compose the link. Audience lists, orders, drafts and body text are not read. Calls go solely to api.linkedin.com, the single host permitted, and your token stays encrypted at rest without ever travelling back to the browser.

Honest limits

• There is no sign-in button. You generate the token yourself and paste it in, and a full OAuth flow is described in the panel as planned for a later release.

• The token lasts 60 days. After that, every share fails until you paste a new one.

• Posts go to the personal profile that owns the token. Company pages are not supported.

• A share is created when an article switches from draft to live. Re-saving a live piece does nothing, publishing again after a share already went out does not repeat it, and earlier articles are not shared retroactively.

• A failure shows on the badge, and the Sync activity page offers a Retry sync button when LinkedIn clearly refused the attempt, such as an expired token or a missing scope. If the request went out but no clear answer came back, the plugin refuses to send again so as not to duplicate the share; check LinkedIn and post by hand if it is missing.

• Reader access is not examined, so a members-only piece is shared with its link as usual.

• The card carries text only. No image is uploaded. The title is cut at 200 characters and the description at 256.

• The LinkedIn post remains if you later unpublish or delete the article.

• LinkedIn does not offer a self-serve OAuth flow for this scope, so authentication is a manually-generated access token you paste in. LinkedIn tokens expire after 60 days and must be refreshed by hand, and the LinkedIn API applies rate limits and posting restrictions that can delay or block a cross-post.

Frequently asked questions

Related plugins

• Bluesky Cross-Post
• X (Twitter) Cross-Post
• Mastodon Cross-Post

Specifications

Category

Social

Price

Included

Version

1.0.0

Source

First-party