#7132·nango

LinkedIn toolkit cannot publish to company page with organization URN due to missing organization scopes

Author: samhaiderCreated Aug 14, 2026Updated Sep 14, 2026
LabelsStale

We are trying to connect with the LinkedIn toolkit to publish social posts for a marketing agent.

The LinkedIn connected account is active, but it authenticates through a personal LinkedIn profile. Our requirement is to publish only to our LinkedIn company page, never to the personal profile.

Company page details:

  • Company name: organizationxyz
  • LinkedIn handle / vanity URL: organizationxyz
  • Company ID: xxxxxxx
  • Organization URN: urn:li:organization:xxxxxxx

Microsoft's LinkedIn URN documentation confirms that organization URNs should be formatted as:

urn:li:organization:{organization id}

So the organization URN appears to be correct.

Expected behavior

Nango should allow the LinkedIn connection to be authorized with the required organization/company-page scopes so that posts can be published as:

json
{
  "author": "urn:li:organization:xxxxxxx"
}

The toolkit should either:

  1. Request the correct LinkedIn organization scopes during OAuth, or
  2. Provide a clear way to create/select an auth config that includes organization posting scopes.

Required or likely required LinkedIn scopes:

w_organization_social
r_organization_admin

Possibly also:

r_organization_social

depending on Nango's verification and lookup flow.

Actual behavior

The LinkedIn connection is active, but organization access cannot be verified or used for publishing.

Organization ACL verification fails

Calling LINKEDIN_GET_COMPANY_INFO for both supported roles fails:

  • ADMINISTRATOR
  • DIRECT_SPONSORED_CONTENT_POSTER

Error:

Forbidden. You don't have permission to access organization ACLs. Ensure you have the r_organization_admin scope.

Direct organization-author publishing also fails

Attempting to publish with:

json
{
  "author": "urn:li:organization:xxxxxxx",
  "commentary": "Test post...",
  "visibility": "PUBLIC",
  "distribution": {
    "feedDistribution": "MAIN_FEED",
    "targetEntities": [],
    "thirdPartyDistributionChannels": []
  },
  "lifecycleState": "PUBLISHED"
}

using LINKEDIN_CREATE_LINKED_IN_POST fails with:

Invalid request: Organization Or Events permissions must be used when using organization as author

This indicates the issue is not URN formatting, but missing organization/event posting permissions on the OAuth connection or auth config.

Reproduction steps

  1. Connect LinkedIn through Nango Connect.
  2. Confirm LinkedIn account is active.
  3. Attempt to verify administered company pages:
LINKEDIN_GET_COMPANY_INFO
role: ADMINISTRATOR
state: APPROVED
  1. Observe the missing r_organization_admin scope error.
  2. Attempt to publish using LINKEDIN_CREATE_LINKED_IN_POST with:
author: urn:li:organization:82348716
  1. Observe the error:
Invalid request: Organization Or Events permissions must be used when using organization as author

Why this matters

For business social-media automation, publishing to a company page is a core requirement. Posting to the authenticated user's personal profile is not acceptable.

In our case, the agent must never fall back to:

urn:li:person:...

It must only publish as:

urn:li:organization:xxxxxx

Request

Please clarify or fix one of the following:

  1. How to reauthorize the existing LinkedIn connected account with w_organization_social and r_organization_admin.
  2. How to create a LinkedIn auth config in Nango that includes company-page posting scopes.
  3. Whether the current linkedin toolkit supports organization-author publishing.
  4. If company-page posting requires a different toolkit, such as linkedin_ads, please document how to create the required auth config, since Nango currently does not auto-initiate auth for linkedin_ads.

Environment

  • Nango via MCP / Connect endpoint
  • Toolkit: linkedin
  • Tool used for publishing: LINKEDIN_CREATE_LINKED_IN_POST
  • Tool used for organization access check: LINKEDIN_GET_COMPANY_INFO
  • Organization author attempted: urn:li:organization:xxxxxxx