Hi @Jon , you are right im not using n8n. I have solved my issue may be others are having the same issue. i’m a laravel developer and the following code is of laravel
$user = Socialite::driver(‘linkedin’)->stateless()->user(); i was passing the linkedin parameter in socialite driver but instead of that we need to pass the linkedin-openid because of the recent change in linkedin products.
$user = Socialite::driver(‘linkedin-openid’)->stateless()->user();
1 Like
I have just put in a PR which can be found below, It adds support for the Community Management API and adds a legacy option to the other API type so that we can support all 3 valid options. Once reviewed this will be available in a future release.
2 Likes
Do you already know in which release it will be available?
Hey @pehaem,
I wanted to have it in 1.13.0 which will be available this week but it looks like due to another LinkedIn API issue that may not happen.
We use the /me endpoint when posting as a person to get the current users ID but it turns out that one of the 3 authentication types doesn’t support it so the question then is do we release this knowing that it won’t work for 1 of the types or do we see if we can get in touch with Microsoft / LinkedIn to find out if this expected.
I have a meeting with our nodes team lead this morning so I will know more shortly.
4 Likes
Hi, does there happen to be any update with this?
1 Like
Hey @cescarsega,
Welcome to the community 
It looks like it is still waiting for a review, I had a quick change to make so I will see if I can get it reviewed when I am back next week.
1 Like
I’m a newbie and I think I did everything right, but it always gives the same error: “Error: Insufficient parameters for OAuth2 callback.
More details
Received following query parameters: {“error”:“unauthorized_scope_error”,“error_description”:“Scope "w_organization_social" is not authorized for your application”,“state”:“eyJ0b2tlbiI6InlTNDVzQVpLLWR3Uy1rdlUtTTc3dWg4NWUwdnJER1I5RjMtQSIsImNpZCI 6IndUSkFHUjJ4Uzh4NDcwTFEifQ==”}
Failed to connect. The window can be closed now.”
Any news to resolve this or does Linkedin remain inaccessible for automatic sharing via OAuth/N8N?
I managed to connect by changing the url and removing the scope parameters that LinkedIn does not authorize.
However, it obviously didn’t work, as you need your personal ID to post. I tried to do it via HTTP Request, it returns some fields, but the personal ID does not because it is not in scope, I spent an afternoon trying to understand why it did not return the id together. Anyway, wait and see what happens.
Hey @mmp,
The userinfo doesn’t always return the id so we have to use 2 different API calls depending on the linkedin product being used.
I will push for a review on the change again so we can get this fixed.
1 Like
I was able to access only the ones in the image below.
From what I’ve found, the one that returns the ID is the end point v2/me. However, it’s from another product.
Hi Jon,
Just wanted to see if any progress has been made on this? I’ve built a content marketing workflow and it’s a shame LinkedIn isn’t working. I’m loving n8n aside from this one issue! 
+1 from me, my content marketing workflow is also stuck due to this one thing.
1 Like
I have bumped the review internally again, I think it just got missed but keep an eye on feat(LinkedIn Node): Add support for Community Management API by Joffcom · Pull Request #7451 · n8n-io/n8n · GitHub
2 Likes
Would be great to get this working, posting to LinkedIn is key!
I just applied to the marketing API (wish me luck!)
and I got this notice:
If you are seeking access to our Page Management APIs, we plan to launch a new Community Management API by early 2023 . You will be required to migrate by applying to the new API and will need to update your integration accordingly.
@Jon any updates on this? I see the pr has been approved
Hey @peacefuldevki,
Welcome to the community 
The PR tests failed so I merged in the latest master branch, Got it approved again and now I just need to click the big green button. This change will be in the 1.26.0 release next week, I just have a tiny bit of documentation to do for the changes and we are good to go.
2 Likes
New version [email protected] got released which includes the GitHub PR 7451.
1 Like
Hello, any solution? Thanks!
Hey @tris,
Part of this is solved but a recent change to LinkedIn has prevented media uploaded from working again which I need to dig into again.