Help Needed: LinkedIn OAuth2 "Bummer, something went wrong" - Redirect URI Mismatch

Questions
22

So we got the HTTP Request node set up and working, but we’re stuck on finding the numeric LinkedIn member ID that the API requires. Still troubleshooting that part, but the HTTP approach itself is solid once we crack the ID issue.

23

For the LinkedIn numeric member ID - you can get it by calling the /v2/userinfo endpoint (OpenID Connect) with your access token. It will return a sub field which is your member URN. Or use the /v2/me endpoint which returns id directly.

In n8n with HTTP Request node: set URL to https://api.linkedin.com/v2/me, add header Authorization: Bearer {{your_access_token}}, and the response will include the numeric id field you need.

Alternatively, if you’re using the LinkedIn node in n8n (not HTTP Request), some older operations still expose the member ID in the response from /v2/me automatically. Depends on which API version you’re targeting.

24

This isn’t an n8n issue it’s a LinkedIn permissions (scope) issue

The error:
Scope "organization social" is not authorized for your application
means your LinkedIn app is requesting a permission it hasn’t been approved for.

What’s happening

  • Your OAuth flow is working correctly (the callback is reaching n8n)
  • LinkedIn is rejecting the request because your app doesn’t have access to that scope
  • w organization_social is part of LinkedIn’s Marketing / Community Management APIs, which require approval

How to fix it

Option 1 (quick fix):
Remove the w_organization_social scope from your n8n credential and use only basic scopes like:

  • r_liteprofile
  • r_emailaddress

This will allow the connection to work, but with limited functionality.

Option 2 (proper solution):
Apply for access to LinkedIn’s Marketing / Community Management API:

  • Go to your LinkedIn Developer app
  • Request access to the Marketing Developer Platform (or relevant product)
  • Wait for LinkedIn approval

Once approved, the scope will work.

Important

LinkedIn is strict with permissions you cannot use advanced scopes unless your app is approved, and it will block the OAuth connection if they’re included.