Linkedin Node throwing issue

Questions
1

Problem

Trying to post content on LinkedIn via the Linkedin node in n8n. But it is showing error.

What is the error message (if any)?

The error message says this:
Your request is invalid or could not be processed by the service

Requested version 20250401 is not active

image
image3386Ă—2086 440 KB

Information on your n8n setup

  • n8n version: 2.16.1
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu
3

Hey Konger

I know exactly what is causing this. The issue isn’t with your post content; it is a versioning issue with LinkedIn’s API.

LinkedIn regularly retires older versions of their background systems. That error Requested version 20250401 is not active means your n8n node is trying to talk to LinkedIn using an API version from April 2025 that LinkedIn has officially shut down.

The Fix: You just need to update your n8n instance to the latest version. The n8n team regularly patches their nodes to use the newest, active API headers whenever platforms like LinkedIn make these deprecation changes.

Once you update n8n, that node will automatically start using the correct, active LinkedIn version and your posts will go through. Let me know if you need help running the update!

Best,

Micheal

4

@Snehasish_Konger if updating n8n isn’t an option right now, swap the LinkedIn node for an HTTP Request node and hit https://api.linkedin.com/rest/posts directly — set the header LinkedIn-Version to 202401 or whatever version is currently active. that way you control the version yourself instead of waiting on the node to catch up.

5

Hi Micheal,
Thanks for the information, but my n8n instance is already updated to the latest version, and yet its not working. I’ve checked it once again.

6

Updating n8n won’t fix this one — the issue is that the LinkedIn node itself is hardcoding 20250401 as the API version header, and that format is wrong. LinkedIn’s REST API uses 6-digit versions (YYYYMM), like 202501 or 202504. The node is sending an 8-digit value (20250401) that LinkedIn doesn’t recognize as a valid version at all.

The workaround achamm mentioned is the right move. Here’s the exact setup:

HTTP Request node config:

  • Method: POST
  • URL: https://api.linkedin.com/rest/posts
  • Auth: OAuth2 (your existing LinkedIn credential)
  • Headers:
    • LinkedIn-Version: 202501
    • X-Restli-Protocol-Version: 2.0.0
    • Content-Type: application/json

Body (JSON):

{
  "author": "urn:li:person:YOUR_PERSON_ID",
  "lifecycleState": "PUBLISHED",
  "specificContent": {
    "com.linkedin.ugc.ShareContent": {
      "shareCommentary": {
        "text": "Your post text here"
      },
      "shareMediaCategory": "NONE"
    }
  },
  "visibility": {
    "com.linkedin.ugc.MemberNetworkVisibility": "PUBLIC"
  }
}

Replace YOUR_PERSON_ID with your LinkedIn member ID (you can get it by calling https://api.linkedin.com/v2/userinfo with your credential).

This bypasses the broken node version entirely and gives you full control over the API version header going forward.