Hi all !
I’m trying to connect a LinkedIn Organization Page (not a personal profile) using the LinkedIn node in N8n. My goal is to publish posts directly on my SaaS company page via a workflow.
The personal account connection works fine. But when I try to connect the organization page using OAuth2, I get the following error when clicking “Connect my account”:
Error: Insufficient parameters for OAuth2 callback.
"error": "unauthorized_scope_error",
"error_description": "Scope "w_organization_social" is not authorized for your application"
What I’ve done so far:
Created a LinkedIn Developer App
Verified the app in LinkedIn Developer Portal
Set the correct OAuth2 Redirect URL (https://n8n.example.com/rest/oauth2-credential/callback)
Enabled all permissions available in the app settings
Linked the app to the Organization Page
But the w_organization_social scope still seems to be unauthorized. I can’t find how to request or unlock this permission in the LinkedIn App dashboard or support documentation.
My question
- Is there a known way to get access to the
w_organization_socialscope for LinkedIn Org posting via N8n? - Does the N8n LinkedIn integration officially support Organization-level posting (not just personal accounts)?
- Are there any additional configuration steps or LinkedIn approval processes needed?
Notes
- I’ve read the LinkedIn node documentation on the N8n site, but it doesn’t cover this use case.
- I’m happy to provide logs or test more if needed.
Additional Info: possible outdated documentation?
I found this line in the official N8n LinkedIn credentials documentation:
“To post as an organization, you need to put your app through LinkedIn’s Community Management App Review process.”
That links to this page:
Community Management App Review - LinkedIn | Microsoft Learn
However, this LinkedIn doc now opens with a Deprecation Notice, stating that the Community Management API and review process have been deprecated and replaced by a new process for getting access to organization-level permissions.
This means the information in the N8n documentation may no longer be valid, and could be misleading for anyone trying to implement org posting in 2025.
I believe this might be part of the issue — if so, is there a plan to update the LinkedIn integration in N8n to reflect these changes? Or do you have any workaround that users can follow in the meantime?
Thanks a lot for your support ![]()


