Skip to main content
Publish individual member posts to connected LinkedIn accounts. Multiple posts are sent in order as separate posts; Posted does not turn them into a LinkedIn reply thread.

​
Connect an account

1

Configure the provider

The installation operator supplies POSTED_LINKEDIN_CLIENT_ID and POSTED_LINKEDIN_CLIENT_SECRET to both API and worker. Enable the identity and member-sharing access needed by Posted in your LinkedIn application. This integration publishes as the authorized member; it does not provide organization-page publishing.
2

Authorize the account

A team administrator opens Connections → Add connection, chooses LinkedIn, and completes the provider’s sign-in and consent flow.
3

Choose it in the composer

After returning to Posted, confirm that the account is Connected. Select it through Choose Accounts, review its preview and customize its text or media if needed.
Accounts belong to the team. Connecting the same provider account again refreshes the existing connection. Members can compose for connected accounts; only administrators can add or disconnect them.

​
Application configuration

Register the exact API callback in your provider application:
Replace the example origin with your API origin. For the hosted installation, it is https://posted-api.avgeek.ltd/api/social/callback/linkedin. Posted requests openid profile w_member_social. Set POSTED_LINKEDIN_API_VERSION to the API version supported by your installation. Posted 0.2.0 uses 202609; keep the value synchronized on API and worker. See configuration for the shared runtime environment and Towbar provider setup for private value entry. Follow the provider’s official authorization documentation for its registration and approval process.

​
Limits enforced by Posted

These are Posted’s current delivery limits. Use list_providers or the provider API endpoint to inspect the running installation’s capabilities. Uploaded originals are prepared for the provider at delivery time; provider account permissions and quotas still apply.

​
Posts, media and threads

Use images or one video for each post. For a sequence, account previews keep individual posts visually separate. Later posts still wait for the preceding item on that account to publish successfully. Each post has independent text and attachment order. Account-specific edits affect only that account and post. Reset to master restores text and media inheritance after confirmation. Image or video publishing requires private media storage. Read Compose a post for single posts and Compose threads for insertion, ordering, reply links and failure handling.

​
Reconnect and troubleshoot

If the account needs reauthentication, an administrator repeats the official authorization flow. If LinkedIn is missing from Add connection, ask the operator to check the complete provider configuration and deploy the saved runtime values. A callback mismatch must be corrected in the provider application using the API origin, not the UI or documentation domain. Inspect Publish history for each account’s result. A confirmed provider publication stays published if another account fails. An Uncertain result needs provider-side inspection before another posting request. Disconnecting prevents later use of the account and does not remove existing provider posts.