Issue with LinkedIn Community Management scopes

[dahmadi]

We have created a new LinkedIn app using the community management api product and have gone through the steps to get it approved by Microsoft/LinkedIn for the Development Tier. Please see the screenshots below. The scopes include rw_organization_admin which is required to access the organizationalEntityFollowerStatistics endpoint to retrieve lifetime follower information:

Organization Follower Statistics - LinkedIn

When using the http request node in n8n for the LinkedIn Community Management OAuth2 API Credential Type only 3 scopes are shown as available:
w_member_social
w_organization_social
r_basicprofile

This is even before selecting the created credential in n8n and remains the same after selecting it. When executing the request (https://api.linkedin.com/rest/organizationalEntityFollowerStatistics?q=organizationalEntity&organizationalEntity=urn:li:organization:{organization ID}) - the following 403 error is returned

Please note the {organization ID} above actually contains our company 8 digit org id. I did not include it above.

403 - "{\"status\":403,\"serviceErrorCode\":100,\"code\":\"ACCESS_DENIED\",\"message\":\"Not enough permissions to access: partnerApiOrganizationalEntityFollowerStatistics.FINDER-organizationalEntity.20240901\"}"

The LinkedIn-Version parameter is passed in the header and I can successfully use the Community Management OAuth2 credentials to use the administered organization lookup
https://api.linkedin.com/rest/organizations/{organization ID}

Am I missing a step here? Authentication works fine, but the limited scopes in n8n seems to be an issue. Thank you for your help.

**n8n version: 1.61.0 (cloud)
**Database (default: SQLite): default
**n8n EXECUTIONS_PROCESS setting (default: own, main):
**Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
**Operating system:

[Jon]

Hey @dahmadi,

You have nailed it, The credential only includes the scopes we actually use in the node so at the moment if you wanted to add more scopes to it you would need to create a generic oauth 2 credenital instead.

This is probably something we should change in the future so if being used with the http request node more scopes could be added.

[dahmadi]

@Jon - Thank you! Got it up and running now using a generic OAuth2 credential