LinkedIn Node API deprecated

Questions
1

Describe the problem/error/question

When trying to post to LinkedIn today, error occurs. I would assume the node needs updating.

What is the error message (if any)?

Your request is invalid or could not be processed by the service

Requested version 20240401 is not active

Information on your n8n setup

  • n8n version: 1.88.0
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Unraid
3 Likes
2

I faced the same issue today and I also posted a topic. I hope it’ll be solved soon.
https://community.n8n.io/t/your-request-is-invalid-or-could-not-be-processed-by-the-service-error-on-linkedin/101938

1 Like
3

Same issue here.

4

I have the same problem too - I have notified github.

5

It looks like there’s a bug in the LinkedIn node.
There are already GitHub issues tracking this:

Until this is resolved, you can still use the HTTP node to make a LinkedIn post. Here’s a simple workflow — feel free to edit it to suit your needs.

2 Likes
6

this is for sharing post with an image.

7

Great job. But how did you got the PERSON_ID value ?

8

Use the linkedin node with your credentials. In the node select Person. If your credentials are correct you will see your name. On this input choose ‘expression’ instead of ‘Fixed’. You will see your PERSON_ID here.

9

Thank you. For me it is still not working, now I have an error for the last node, I think it might be related to the scopes :

400 - "{\"errorDetailType\":\"com.linkedin.common.error.BadRequest\",\"message\":\"com.linkedin.content.common.exception.BadRequestResponseException: One or more of the contents is not owned by the author. All contents must be owned by the author\",\"errorDetails\":{\"inputErrors\":[{\"description\":\"Content(s) you provided must be owned by post author\",\"input\":{},\"code\":\"INVALID_CONTENT_OWNERSHIP\"}]},\"status\":400}"
10

Thanks for sharing this. Can I buy you a coffee? Do you prefer ice cream?

11

Thanks man. If I could help you this is enough for me :pray:

1 Like
12

Is the PERSON_ID belongs to the account which is the owner of the page?

13

Yes, that is correct. I don’t have the Community Management API product activates, is the one you use ?

14

No I dint’t activated any external API. I just used regular HTTP requests and linkedin auth credentials. Did you check your linkedin developer console. is “w_member_social” scope active ?

15

I havn’t yet understood all, but I was trying to use DALL E to generate the image. I finally found a solution:

image
image2978×806 165 KB

I don’t know how to share the workflow, I’ll try the preformatted text :slight_smile:

16

Hey all, the fix was deployed in 1.90.0 today. If you need it urgently, feel free to update to ‘latest beta’ (if you’re on cloud), which by now is 1.90.1.

2 Likes
17

I Can show you!

18

this error appears “Your request is invalid or could not be processed by the service
ERROR :: /author :: “urn:li:person:PERSON_ID” does not match urn:li:company:\d+|urn:li:member:\d+”
I am pretty stuck here because i didnt find the person_id and if i change for other i think is the one the same error keeps appearing.

19

If you used my workflow, the person id should be retrieved dynamically from the “Get User URN” node. Is that node working correcly in your case and only the last node fails ?

image
image1710×1548 179 KB

20

can you share the last version of the code?, the one i downloaded from a threat is not even closer to what you just share with me. some .json to import, please?