Error in Image Upload for LinkedIn

Describe the problem/error/question

I am able to make normal TEXT post in linkedin. If I want to make a post with Image, I am facing issue, I checked this thread and its not relevant

currently in version 1.29.1

What is the error message (if any)?

Please share your workflow

1 Like

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
  • n8n version: 1.29.1
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Default
  • Running n8n via (Docker, npm, n8n cloud, desktop app):. - docker
  • Operating system: apple M1

Hey @AJ_J,

Welcome to the community :cake:

There is another post open for this issue as well, Can you share which products you have enabled in your LinkedIn app and which credential type you are using.

Thanks for your reply

following are the products selected

Hey @AJ_J,

Which credential are you using?

I am using linkedin ouath 2 qpi.

@Jon any valuable suggestion?

@AJ_J not yet it is a weekend so I won’t be checking it until Monday

Pls advise if you have any solution

Hey @AJ_J,

I have managed to reproduce it but have not had a chance to fix it yet.

1 Like

Any luck mate

Still on the list sadly, Once it is fixed an update will be posted here.

1 Like

+1 for me.
I’m facing the same issue.

Posting to LinkedIn works fine, but fails if I’m trying to include binary data either as an image post or when adding the thumbnail data for an article post.

  • n8n version: 1.32.2
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Default
  • Running n8n via (Docker, npm, n8n cloud, desktop app):. - docker
  • Operating system: Ubuntu 22.04

Hey there ! Same here, I managed to handle it with HTTP requests

I am able to post LinkedIn images on version 1.16.0. Did not try to upgrade, and as long as it is working, I prefer to stay on my version

1 Like

Hey @Martin_Neumann,

That is interesting, If 1.16.0 is working this means the change is outside of the node and is related to a core issue. I will update the notes in the ticket.

Hi, can you please share the workflow you used to workaround the issue using the HTTP request?

This may now be fixed in 1.41.1 which updates the api version.

2 Likes

Confirmed this issue still exists in 1.41.1 self hosted (posting as Organization)