Skip to content

LinkedIn

For the administrator: what to set up so people can press Connect with LinkedIn, and optionally post as a company page. Without it, the LinkedIn card accepts a pasted token instead.

In the LinkedIn developer portal

  1. Create an app, associated with the company’s LinkedIn page.
  2. Under Auth, add <PULSE_PUBLIC_BASE_URL>/oauth/social/callback to the authorized redirect URLs (see Public address and redirects).
  3. Under Products, add Sign In with LinkedIn using OpenID Connect (scopes openid, profile) and Share on LinkedIn (w_member_social). That is all a person needs to post as themselves.
  4. To post as a company page, request the Community Management API. Once LinkedIn approves it, the app may ask for r_organization_social, w_organization_social and rw_organization_admin.

In PULSE

SettingWhat to set
LINKEDIN_CLIENT_ID, LINKEDIN_CLIENT_SECRETThe app’s client id and secret (the secret from the instance’s secret store). With both and an https PULSE_PUBLIC_BASE_URL, the card shows Connect with LinkedIn.
LINKEDIN_COMPANY_PAGEStrue only after LinkedIn approved the Community Management API. The card then also offers Connect company pages, which asks for the three page scopes and lists the pages the member administers to post as.

LinkedIn access tokens last 60 days. PULSE renews one in its last ten days only when LinkedIn issued a refresh token (LinkedIn does that only for apps it enabled for programmatic refresh); otherwise the card shows “reconnect before” the date. Disconnect revokes the token at LinkedIn, then deletes it.

Connecting publishes nothing. LinkedIn posts also need PULSE_APPLY_ENABLED, PULSE_PUBLISH_LINKEDIN and the content owner in PULSE_PUBLISHER_USER_IDS; the daily LinkedIn draft is never scheduled by itself. See Switches and arming order.