Connection to LinkedIn fails: "unauthorized_scope_error" / "Scope 'openid' is not authorized for your application"

[noch1oliver]

I used to be able to connect my n8n cloud instance to LinkedIn via the LinkedIn node and post text. At one point, I had to delete the credentials. Now, I am unable to reconnect. Any attempt fails. (Hint: I also updated the app to 1.93.0)

What I tried:
- Deleted browser data
- Retried on Chrome
– Retried on Safari, Incognito & Non-Incognito
- Deleted old n8n-connections in LinkedIn (Available Services, “Zulässige Serviceleistungen”)
- Created a new (dummy Account) on LinkedIn
- Tried Legacy setting to ON

Person Name or ID is marked with the error “Issues: There was a problem loading the parameter options from server: “Unable to sign without access token””

After creating a new Account (Toggles: “Standard”, “Organization Support”: OFF, “Legacy”: Off) I get a popup with an n8n-error-image which switches to an error text:

Error: Insufficient parameters for OAuth2 callback.

More details
Received following query parameters: {"error":"unauthorized_scope_error","error_description":"Scope "openid" is not authorized for your application","state":"eyJ0b2[...]"}
Failed to connect. The window can be closed now.

The green banner indicating a successful connection, doesn’t appear.

How can I (re-)connect my n8n cloud instance to LinkedIn?

Thx for your help, community!

---

n8n version: [email protected]
Database (default: SQLite): default
n8n EXECUTIONS_PROCESS setting (default: own, main): ?
Running n8n via (Docker, npm, n8n cloud, desktop app): cloud
Operating system: MacOS 15.4.1

[King_Samuel_David]

@noch1oliver

openid

Hm, and your on cloud, so it seems ‘openid’ is the scope, you could try manually make a connection with your own app and add the scope if that helps,

I don’t use cloud, but it seems you could use HTTP node, with oauth2 and follow the below.

or may try with

LinkedIn credentials | n8n Docs

Hope this helps.

[noch1oliver]

Ahh, this could be an approach. Thanks for pointing out the useful resources I had missed before.

Had the impression, both sides negotiate stuff on the backend and I am unable to intervene. At least for the n8n-side that’s not true. With the customizable OAuth2 Credential Options I get more agency. I will wrap my head around it and try to fix it the n8n-way.

Thanks a lot!
Oliver