LinkedIn node fails with NONEXISTENT_VERSION 20250401 in n8n Cloud 2.15.x

Feature Requests
1

I am getting a LinkedIn API error when using the n8n LinkedIn node.

Error:
Requested version 20250401 is not active (NONEXISTENT_VERSION, HTTP 426)

Node:
LinkedIn → Create Post

n8n version:
2.15.1 (Cloud)

Issue:
The node fails before request execution due to invalid LinkedIn API version header.

It looks like the node is sending:
LinkedIn-Version: 20250401

But LinkedIn rejects it as an inactive API version.

Expected behavior:
Node should use a valid LinkedIn API version or allow overriding the API version.

Actual behavior:
All LinkedIn post requests fail immediately with HTTP 426.

Workaround:
Using HTTP Request node with LinkedIn-Version: 202401 works correctly.

Stack trace:
{
“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”: “Publish to LinkedIn”,
“nodeType”: “n8n-nodes-base.linkedIn”,
“nodeVersion”: 1,
“resource”: “post”,
“operation”: “create”,
“time”: “4/16/2026, 11:51:37 AM”,
“n8nVersion”: “2.15.1 (Cloud)”,
“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:103: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:1670: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:2315:11"
]
}
}

2

Same here. did you find any solution ?

3

Check Linkedin native node not working · Issue #28559 · n8n-io/n8n · GitHub

4

I am facing same problem.

Here is the reason :

LinkedIn now uses a “Quarterly Versioning” system. Each version is only supported for one year. Because your node was built to use the April 2025 version, it expired exactly one year later—yesterday.

I am trying to delete node and adding it again.

5

Hi, I have the same problem. New node will not work.

6

Still not get any solution ,

7

Hi @Tech_Consulting, this is a really annoying bug.

The problem is that the LinkedIn node in n8n is sending the header LinkedIn-Version: 20250401, which has 8 digits in the format YYYYMMDD. However, the LinkedIn API doesn’t use days; it uses the format YYYYMM, meaning 6 digits. April 2025 would be 202504, not 20250401. That’s why LinkedIn returns 426 NONEXISTENT_VERSION; it literally doesn’t recognize this version.

Your workaround with the HTTP Request node passing LinkedIn-Version: 202401 is the correct way for now. Keep using it that way, and it will work; the LinkedIn OAuth credentials will follow normally in the HTTP Request.

Regarding the bug itself, it’s worth opening an issue on the n8n GitHub if you haven’t already:

Search for “LinkedIn NONEXISTENT_VERSION” before opening it to avoid duplication. If it already exists, just add a +1 with your version to make it visible.

Regarding the credentials disappearing after the update you mentioned, that’s a different problem. When n8n Cloud updates, sometimes the link between the node and the saved credential is lost, but the credential itself remains. Go back into the node settings and select the existing credential from the list; don’t create a new one. If it appears duplicated, you can delete the older one later.

(If you want a more robust version of the workaround, try LinkedIn-Version: 202504 instead of 202401 — it’s the most recent version in the correct format and may have more features available.)

Next time, send your questions to the Questions tab so the community can respond faster. If this solution helped you, please also hit the heart button.

Stay well and all the best!

1 Like
8

Have any one getting any solution how to update that LinkedIn-Version: 20250401 Node ?

9

check please

10

I am also getting same exception. I am using n8n from local machine.
Updated the n8n software to the latest version using npm command. Now above issue is resolved.