LinkedIn 403 Forbidden Error when Posting as Person

I know others have had this issue but I did not see any resolution for it. I am creating a standard oauth connection, where I log into my account, but despite the connection being good, I cannot create a post in LinkedIn at all. I get the 403 forbidden error every time.
For the record, I have the same type of connection in Make.com and it works fine. Not sure what else I can do.
I appreciate any help.

Information on your n8n setup

  • n8n version: ? cloud
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: windows 11

Hey @Anthony_Lee,

Which credential type are you using? We have 3 different options and the one to use would depend on the product configured in LinkedIn.

When posting as you using the ID that is fetched from the api and do you have the organisation support option enabled?

So, I only see two connection options.

I’ve tried both. When I use Community Management, whenever I get to the part where I am to connect, it just says Oops, there was a problem.

When I use standard, it does connect (cuz I just have to log in), but again, I’m forbidden from ever posting anything. But, I leave all of the options as default, so yes, organization support is on.

Hey @Anthony_Lee,

If you are posting as a person the Organization Support option needs to be disabled.

I have however just put in a fix that prevented the user details from loading.

1 Like

Unfortunately, now I cannot save my credentials. It says that it got saved but it doesn’t actually save.

Hey @Anthony_Lee,

You would need to click Connect My Account again then save.

That’s what I am trying to tell you. I did. And nothing happens. The screenshot I attached is exactly what it looked like after I clicked to connect my account. And it wouldn’t let me save. It kept saying that it already saved. But, yea, it isn’t happening.

What happens when I click to connect.

What happens after I try to close the window.
n8n-still-not-connected

And, still, when I try to post…I get the same permissions error.

Hey @Anthony_Lee,

That is odd however you may also need the fix I mentioned which is not yet released. The fix has been merged and should be available in the next release which will likely be going out tomorrow.

New version [email protected] got released which includes the GitHub PR 9912.

NEW UPDATE
After toggling BOTH Organization and Legacy OFF I was able to connect my account (by logging in) but STILL I get 403 error whenever trying to post…

NodeApiError: Forbidden - perhaps check your credentials?
    at Object.linkedInApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/LinkedIn/GenericFunctions.js:49:15)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/LinkedIn/LinkedIn.node.js:216:40)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:728:19)
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:664:51
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1076:20

My app does have the necessary scopes, however.

Are you now on 1.49.0?

Ah. No.
I switched over to the community version on Railway. I used one of the templates (N8N W/ Workers) and I’m on Version 1.47.3

So I’d imagine that’s the problem. Unfortunately I have no idea how to update to the latest version.

Thank you though.

Hey @Anthony_Lee,

There are so many deployment tools now, Does Railway work from a docker file in a GitHub repo? It could be a case of adding the version to the end of the docker image.

Yes, Railway works from a docker file. but as a no-coder, everything you just said sounded like Mandarin. lol

Can you share your dockerfile?

Unfortunately, I used a template so it doesn’t look like I have access to that (I can’t find it in the Railway app anyway)

Ah, Did you have to make a Github repo for it or anything?

No. Just searched templates, found the one with n8n and workers (and Postgres and Redis) and clicked to download it.
It deployed from Dockerhub and links to this - https://hub.docker.com/r/n8nio/n8n

Unfortunately I was never able to figure out how to update n8n in this cloud instance, so I installed locally and have been using it on my machine. I updated successfully and can say that YES, the issue has been resolved. Linkedin Posting now works for me. Cheers!

1 Like