Connect LinkedIn and publish to your member profile
Use LinkedIn member consent for professional text or image posts and verify the result on the authorised profile.
Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.
Social accounts → LinkedIn; Configuration where applicable
PermissionManage connections; administrator for app credentials; Create posts + Publish posts for a live test
Before you begin
A LinkedIn developer app with the required sign-in and member-posting products, plus an authorised member account. Provider app/Page ownership verification may be required by LinkedIn.
Follow these steps
- In Configuration, copy the LinkedIn application callback into the matching provider app. Save its matching ID and secret with Save encrypted credentials. Leave direct publishing locked during connection setup.
- Choose LinkedIn Connect and approve the member identity and requested posting access in LinkedIn’s official consent flow.
- In Social accounts, choose Verify connection and compare the account or destination identity with the intended test account.
- Use text or a JPEG/PNG image and keep the complete composed text within 3,000 characters. Video is not supported by this adapter.
- When a controlled test is authorised and the direct gate is enabled, select only this destination, choose Post Now once and inspect its existing receipt.
Fields and options
- Requested OAuth permissions
- openid, profile and w_member_social. These are the scopes requested by the current adapter; provider products/review must permit them.
- Destination and scope
- The current adapter targets the connected member profile with public post visibility. It does not implement organisation/Company Page publishing.
- Publishing format
- Use text or a JPEG/PNG image and keep the complete composed text within 3,000 characters. Video is not supported by this adapter.
Rules and limits
- Saving credentials or passing connection verification does not prove that a live publication succeeded.
- Use a dedicated test destination and the most restrictive appropriate visibility. Provider consent, app review and organisational approvals remain separate requirements.
Check the result
- Open the connected member’s recent activity and check the published text/image. A remote post reference may be available without a public permalink.
- Match the actual provider outcome to the destination receipt, remote reference and intended visibility.
If something does not look right
- If member publishing is denied, check the Share on LinkedIn/member-posting product and w_member_social grant. A Company Page admin role does not change this adapter into a Page publisher.
- Do not repeat Post Now after an ambiguous result until the original provider outcome has been checked.
Common questions
Does a connected account mean publishing is approved?
No. Connection identity, app publishing entitlement, content eligibility and the separate direct-publishing gate are independent checks.
What is a complete first test?
Official consent, correct destination discovery, successful verification, one deliberate test publication, a destination receipt and direct verification in the actual provider account.