Error with the linkedin node

Questions
1

Hey. I am not able to get the linkedin node working in n8n

Describe the problem/error/question

{
“errorMessage”: “Your request is invalid or could not be processed by the service”,
“errorDescription”: “Requested version 20250401 is not active”,
“errorDetails”: {
“rawErrorMessage”: [
“426 - {"status":426,"code":"NONEXISTENT_VERSION","message":"Requested version 20250401 is not active"}”
],
“httpCode”: “426”
},
“n8nDetails”: {
“nodeName”: “Create a post”,
“nodeType”: “n8n-nodes-base.linkedIn”,
“nodeVersion”: 1,
“resource”: “post”,
“operation”: “create”,
“time”: “4/18/2026, 10:50:27 AM”,
“n8nVersion”: “2.16.1 (Self Hosted)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: [
“NodeApiError: Your request is invalid or could not be processed by the service”,
" at ExecuteContext.linkedInApiRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/LinkedIn/GenericFunctions.ts:71:9)“,
" at processTicksAndRejections (node:internal/process/task_queues:104:5)”,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/LinkedIn/LinkedIn.node.ts:182:31)“,
" at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1045:8)”,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1224:11)“,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1672:27”,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2324:11"
]
}
}

What is the error message (if any)?

Please share your workflow

CHAT, AI AGENT, LINKEDIN TOOL

Share the output returned by the last node

<HI NICE TO MEET YOU

Information on your n8n setup

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

Hi @ArcCreat_Ions

Your options to fix this:
since you’re on n8n version 2.16.1 and the official fix has been merged but not yet released , you can patch it manually.

  1. If you’re running n8n via Docker, run this command inside your container:

sed -i "s/'LinkedIn-Version': '[0-9]*'/'LinkedIn-Version': '202604'/" /usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/LinkedIn/GenericFunctions.js

Then restart n8n .

Note: You’ll need to re-run this after each n8n update until the official fix ships.

  1. use the HTTP request node

Replace your LinkedIn node with an HTTP Request node, this gives you full control over the API version

Method: POST - URL: https://api.linkedin.com/rest/posts - Headers: Add LinkedIn-Version 202604

Body (JSON):

{
“author”: “urn:li:person:{{YOUR_PERSON_ID}}”,
“lifecycleState”: “PUBLISHED”,
“specificContent”: {
“com.linkedin.ugc.ShareContent”: {
“shareCommentary”: {
“text”: “{{$json.yourPostContent}}”
},
“shareMediaCategory”: “NONE”
}
},
“visibility”: {
“com.linkedin.ugc.MemberNetworkVisibility”: “PUBLIC”
}
}

The HTTP node uses the 6-digit format YYYYMM (like 202604), while the error message shows 20250401 (8 digits). The LinkedIn API expects the 6-digit format

Let me know which approach works best for your setup :crossed_fingers:

5

welcome to the n8n community @ArcCreat_Ions
I checked the repo, and the LinkedIn fix has already been merged, but it appears to have landed after the latest public release, so I would not expect it to be included in the current release yet. In the meantime, I would temporarily publish via an HTTP Request node using an active LinkedIn API version header instead of the built-in LinkedIn node.

6

@ArcCreat_Ions bypass the broken LinkedIn node entirely, that NONEXISTENT_VERSION error means n8n is sending a dead API version header and no amount of restarting fixes it until the next release ships. use HTTP Request instead:

swap YOUR_PERSON_ID with your LinkedIn member URN, set up OAuth2 credentials on the HTTP Request node with your existing LinkedIn app client id/secret, done.