Hello Team
I’ve been experiencing trouble connecting my LinkedIn account in n8n and wanted to flag it in case others are running into the same thing.
Here’s what’s happening:
403 - {“message”:“”,“status”:403}
If you’ve faced this and found a fix, I’d love to hear what worked. Drop it in the comments!
Hi @sachin_verma
If you’re trying to post as an individual/personal account (not an organization), the most common cause of this 403 error is having Organization Support enabled in your credential settings. Disabling it resolves the issue for most users.
HI @sachin_verma Welcome
This can be caused by not giving right permissions also, i would say you should consider revoking your current API credentials and then creating a new one fresh then try again.
Thanks for your comment Anshul. I have created thrice credential as per n8n documentation, but still facing same issue.
@sachin_verma have you tried ensuring that “Share on LinkedIn” and “Sign In with LinkedIn using OpenID Connect” are both requested and Approved? and some scopes are needed like:
openid profile w_member_social email
Let me know if these boxes are checked as well.
yes @Anshul_Namdev All has approved and same scope is also defined
Understood, have you tried using an HTTP node for this? I guess that would work.
Read this:
ok let me try with http node for the same. Please allow me 10-15 mins and come back with updated status. Thanks a lot
@sachin_verma You need to disable the option, not enable it. and If you created a brand new LinkedIn App recently, try toggling The “Legacy” Toggle OFF. New apps often only work with the latest Version 2.0 API scopes.
I am not able to find text box on credential popup as well as unable to get callback url. n8n has been upgraded they are not required as of now.
Yes, the solution is to disable ‘Organization Support’ toggle button at the time of creating LinkedIn credentials. It works well after that.
@sachin_verma — just to add some more diagnostic detail to what the others said, since I ran into this exact issue when I built LinkedIn automation into my own business workflows.
The 403 with an empty message body is almost always one of two things: the Organization Support toggle (as @A_A4 mentioned — disable it for personal accounts) or a LinkedIn App product mismatch. If you created your app recently, make sure you actually added the “Share on LinkedIn” product AND the “Sign In with LinkedIn using OpenID Connect” product to the app in the LinkedIn Developer Portal — both need to be active and approved, not just requested.
One thing that catches people: LinkedIn sometimes shows the products as “In Review” for days, and the OAuth flow will technically complete, but you will get a 403 on actual API calls because the scopes are not actually granted yet. Go to your LinkedIn Developer App → Products tab, and verify both products show a green “Added” status, not “Pending” or “In Review.”
If all that checks out and you are still hitting 403 specifically on POST requests to share content, check which API version your n8n LinkedIn node is using. The node historically targeted older versioned endpoints and LinkedIn is strict about version headers. The current working version header should be 20231101 or later — some older n8n versions send a deprecated one and LinkedIn responds with a 403 instead of a more descriptive error. Upgrading n8n to 1.90+ resolved this silently for me.
