Skip to main content

LinkedIn

Post updates and read your profile on LinkedIn as the connected member.

Connect it with: Sign in (OAuth). LinkedIn's own documentation: https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin-v2.

What agents can do​

Connect LinkedIn so the agents working your tasks can reach it. With it connected, they can:

  • Publish a text post, an article link or an image post on the connected member's feed, when a task asks for it.
  • Comment on or react to a post as the member.
  • Read the member's name and photo to sign a post or a message.

Before you start​

  • A LinkedIn member account. Posting goes out under that member's name, so connect the account that should be the author.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with LinkedIn​

This is the quickest way in: you sign in to LinkedIn and approve what Jaah asks for. You never copy a key.

  1. In Jaah, open Secrets and select New.
  2. Search for LinkedIn and select its card.
  3. Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
  4. Select Connect LinkedIn. LinkedIn's sign-in window opens.
  5. Sign in to LinkedIn if asked, check the access listed, and approve it.
  6. You land back in Jaah on the new secret, which reads Connected once its test passes.

If the button reads Jaah app not configured, this Jaah has no app registered at LinkedIn yet. Use your own OAuth app until it does (see Use your own OAuth app).

Scopes Jaah requests​

Jaah asks LinkedIn for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.

ScopeWhy Jaah asks for itRequired
openidIdentify the LinkedIn member who connected, so the secret shows whose account it isYes
profileRead the member's name and photo, which agents use to sign or attribute postsYes
emailRead the member's primary email address, shown on the secret to tell accounts apartNo — you may untick it
w_member_socialCreate, edit and delete posts, comments and reactions as the member, when a task asks agents to publishNo — you may untick it

Connect with an API key​

LinkedIn has no API key option in Jaah: connect with the sign-in above.

Use your own OAuth app​

Register your own OAuth app at LinkedIn when your company requires apps it controls, or before this Jaah has an app registered there.

  1. Create an OAuth app in LinkedIn's developer console, https://www.linkedin.com/developers/apps/new (LinkedIn's documentation).
  2. Set its redirect URI to https://app.jaah.ai/api/credentials/connect/callback (on your own Jaah, its console address followed by /api/credentials/connect/callback).
  3. Give it the scopes in Scopes Jaah requests.
  4. Copy its client ID and client secret.
  5. In Jaah, start a new LinkedIn secret, select Use your own OAuth app, paste both values and select Connect LinkedIn.

The client secret is stored with the connection, encrypted, like any other secret value.

Test the connection​

Select Test on the secret. Jaah calls LinkedIn's API once (GET https://api.linkedin.com/v2/userinfo) with the stored values, and shows who it answered as, or which value LinkedIn refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A signed-in connection hands the agent its access_token, with access_token_expires_at. LinkedIn issues no refresh token to apps like Jaah, so the token works until that time; then the secret's Test asks you to reconnect.

Tell the agent in your task description which secret to use, for example “use the LinkedIn secret org/linkedin”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Reconnect: when LinkedIn ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at LinkedIn's side too, remove Jaah's access in LinkedIn > Settings & Privacy > Data privacy > Permitted services.

Limitations​

  • LinkedIn grants last 60 days and LinkedIn issues no refresh token to self-serve apps. After 60 days the Test reports the token expired: select Reconnect.
  • Posting to a company page, reading analytics or messaging needs LinkedIn's partner programs (Community Management API, Marketing API), which this connection does not request.
  • Agents cannot read the member's connections, feed or inbox: LinkedIn does not offer those to self-serve apps.
  • Agents can do only what the connected LinkedIn account and its granted scopes allow.

Troubleshooting​

Test says The LinkedIn access token has expired - press Connect to reauthorize

LinkedIn tokens last 60 days and cannot be renewed automatically. Select Reconnect and approve again.

Test says LinkedIn rejected the access token (401)

The member removed Jaah under LinkedIn Settings > Data privacy > Permitted services, or changed the password. Select Reconnect.

Connect stops with unauthorized_scope_error

The OAuth app lacks a product. In the LinkedIn developer portal open the app's Products tab and request Sign In with LinkedIn using OpenID Connect and Share on LinkedIn; or untick the optional scopes.

An agent's post fails with 403 ACCESS_DENIED

The w_member_social scope was unticked at Connect. Select Reconnect and keep that scope ticked.

Still stuck? Select Test and read the result: it names the value LinkedIn refused and the status it answered.

FAQ​

Can agents post to our company page?

Not with this connection. Company page posting needs LinkedIn's Community Management API, which LinkedIn approves per company.

Will posts say they came from Jaah?

LinkedIn shows posts as the member's own. Review what a task will post before you let an agent publish.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one LinkedIn account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.