In cloud platform in the linkedin node in create new credentials and in standard (recommended), it doesnot have client id, client secreat key field? same linkedin node has all these fields in desktop version and hence i am able to create connection to linkedin on my desktop version but not cloud version
Hey @rani_adhaduk !
I think that on Cloud instances this behavior is expected for certain oAuth based credentials, including LinkedIn when using the “stanndard/recommended” OAuth2 methods…(n8n manages that in background when you connect with your account).
In self-hosted instances, we do see Client ID and Client Secret field we must create and configure our own LinkedIin app, as described in tutorial, docs…
So…there is currently no option on n8n Cloud to switch that LinkedIn “standard (recommended)” credential UI to manual Client ID / Secret model, Cloud always uses the managed OAuth app for that flow.
Hope you understood 
Cheers!
Thank you so much! How would i connect to my linkedin account using cloud n8n, i am getting this error.
What am i missing?
Hey @rani_adhaduk !
What you are missing in your LinkedIn App Configuration:
​You need to enable the Sign In with LinkedIn using OpenID Connect product in your LinkedIn Developer App…
You must enable the following products by clicking Request access (or Select i m not sure btw):
​’Signn In with LinkeidIn’ using OpenID Connect (This suppose toprovide the openid, profile, and email scopes.)
​’Share on LinkedIn’ (This provides the w_member_social scope needed for posting.)
Oh, as well be ssure your n8n redirect URL is added to the Authorized redirect URLs. It should follow this format https:://yourn8n..com/rest/oauth2-credential/callback.
So, it s a LinkedIn configurations issue here.
I have done everything mentioned and i still get this error
Do you have reference videos or documentation on how to connect to my linkedin account using n8n cloud?
Thanks
I was able to connect linkedin with my desktop n8n but not able to connect with with cloud account
Couse is not asking the openid scope, vouse you provide all the credentials.
But anyway, for the cloud version I think that the scope openid is required and for the “Sign In with LinkedIn using OpenID .
Be sure to disable in credentials the “Organization Support” as well…
Thank you so much for your help! its fixed now, everything was right from linkedin side but when uisng linkedin node only toggle legacy and off organization support
2 Likes
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.