Linked in credentials not being created

HEY ! i AM STARTING OUT IN N8N , BUT HAVE BEEN STRUGGLING WITH CREATING CREDENTIALS FOR LINKED IN , i HAVE TRIED SOLVING IT BY READING THROUGH THE DOCS BUT THE LATEST UPDATE WHERE IT DOESN’T TAKE CLIENT id AND SECRET FOR STANDARD CONNECTION IS NOT WORKING FOR ME.

Describe the problem/error/question
I am trying to connect to LinkedIn in and build a post automation , hence using the linked in create a post node. However , when I try to create new credential and connect my account it gives an unauthorized_scope_error.
I have configured my linked in developer API correctly ,

  1. Share on Linkedin and Sign In with LinkedIn using OpenID Connect is added
    Image

  2. My Client Secret and Client Id is enabled

  3. Redirect Link is added

Image
4) Scope for personal posting also enabled.

Image
Additionally to test if my LinkedIn developer API is setup correctly , I have made a test automation using HTTP request to post in linked in and it is working perfectly to post it , however I am unsure how to attach an image while posting and hence would need the linked in node for that.
I have added the HTTP request workflow in the workflow section.
What is the error message?
Received following query parameters: {“error”:“unauthorized_scope_error”,“error_description”:“Scope “openid” is not authorized for your application”,“state”:“eyJ0b2tlbiI6IkNzMzk3TzUyLXBQZmxCZzRnaEdJRmRVV3JfNmJDV1ZCZVFCdyIsImNpZCI6InRCRHlIaUdmVjlteHhtcUgiLCJjcmVhdGVkQXQiOjE3NjMzNDkxNTczMjMsInVzZXJJZCI6IjhmNGNmODE3LTM5MzctNGZmMS1iNDA2LTI4OTQyYzNiYjk1OSIsImhvc3QiOiJ0Y2FpYXVhZy5hcHAubjhuLmNsb3VkL3Jlc3QifQ==”}
workflow/screenshots/recording
This is a credential creation problem and I do not have a working workflow with link in node , however as mentioned earlier I have built a workflow using HTTP request and here’s that-
{
“nodes”: [
{
“parameters”: {},
“type”: “n8n-nodes-base.manualTrigger”,
“typeVersion”: 1,
“position”: [
0,
0
],
“id”: “cef84b24-e8f9-486e-ad8b-c790494ada87”,
“name”: “When clicking ‘Execute workflow’”
},
{
“parameters”: {
“url”: “https://api.linkedin.com/v2/userinfo”,
“authentication”: “genericCredentialType”,
“genericAuthType”: “oAuth2Api”,
“options”: {}
},
“type”: “n8n-nodes-base.httpRequest”,
“typeVersion”: 4.3,
“position”: [
208,
0
],
“id”: “c5310611-d183-4278-818e-c2da74bbd0e9”,
“name”: “Get Linkedin Account Info”,
“credentials”: {
“oAuth2Api”: {
“id”: “g7GzpiKCr2zUwRfM”,
“name”: “LinkedIn OAuth2”
}
}
},
{
“parameters”: {
“method”: “POST”,
“url”: “https://api.linkedin.com/v2/ugcPosts”,
“authentication”: “genericCredentialType”,
“genericAuthType”: “oAuth2Api”,
“sendHeaders”: true,
“headerParameters”: {
“parameters”: [
{
“name”: “Content-Type”,
“value”: “application/json”
}
]
},
“sendBody”: true,
“specifyBody”: “json”,
“jsonBody”: “={\n “author”: “urn:li:person:{{ $json.sub }}”,\n “lifecycleState”: “PUBLISHED”,\n “specificContent”: {\n “com.linkedin.ugc.ShareContent”: {\n “shareCommentary”: {\n “text”: “Testing post”\n },\n “shareMediaCategory”: “NONE”\n }\n },\n “visibility”: {\n “com.linkedin.ugc.MemberNetworkVisibility”: “PUBLIC”\n }\n}”,
“options”: {}
},
“type”: “n8n-nodes-base.httpRequest”,
“typeVersion”: 4.3,
“position”: [
416,
0
],
“id”: “e8737f0a-af74-4356-b60e-602b9e507e4b”,
“name”: “Post on Account”,
“credentials”: {
“oAuth2Api”: {
“id”: “g7GzpiKCr2zUwRfM”,
“name”: “LinkedIn OAuth2”
}
}
}
],
“connections”: {
“When clicking ‘Execute workflow’”: {
“main”: [
[
{
“node”: “Get Linkedin Account Info”,
“type”: “main”,
“index”: 0
}
]
]
},
“Get Linkedin Account Info”: {
“main”: [
[
{
“node”: “Post on Account”,
“type”: “main”,
“index”: 0
}
]
]
},
“Post on Account”: {
“main”: [

]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “d50ef648eef86978b2734bd826009baeabaa8d689f8984d0144b98e1a26e8c8c”
}
}
Sharing step by step screenshot of trying to enable the linked in credentials.
Step 1 : Create a new linked in node and clicked on create new credentials -

Step 2 : Unchecked Organisational Support and Legacy , clicked on connect an account

Image
Error -

Alternate Step 2 : I have tried keeping Legacy On and the connect my account , then the pop up asks me to login and Allow N8n permissions , on allowing it does show Connection Successfull -

Step 3: Now , the person field should have my name in it but it doesn’t show , so in expression I mentioned the Name and when I put a text and click on execute , I get a 403 error , which n8n suggest is due to credential problem.

Debug info
core
n8nVersion: 1.118.2
platform: docker (cloud)
nodeJsVersion: 22.21.0
nodeEnv: production
database: sqlite
executionMode: regular
concurrency: 5
license: community
storage
success: all
error: all
progress: false
manual: true
binaryMode: filesystem
pruning
enabled: true
maxAge: 168 hours
maxCount: 2500 executions
client
userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/140.0.0.0 safari/537.36
isTouchDevice: false
End Note
Thanks for looking into this , my understanding is that n8n is picking up the client secret and client id from somewhere , but it’s best if we are able to mention the client id and secret on the standard credentials page so that there is down time when he client id and secret has to be changed.
Suggestions are welcome , if I am doing anything wrong here,

1 Like

same here. Only in the n8n Clou,d on prem is working.

IDK what changed after I raised it in community support and created a ticket as a bug , it started working. However , the last post on linked in node fails while execution with a 403 error but the post gets posted on linkedin.