Issue Station
Sign In
Tools hereToolbox

n8n - ✅(Solved) Fix Linkedin native node not working [1 pull requests, 3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28559•Fetched 2026-04-16 07:04:57
View on GitHub
Comments
3
Participants
3
Timeline
4
Reactions
0
Author
ray007united-rgbray007united-rgb
Participants
bjoernwuestbjoernwuestray007united-rgbray007united-rgbThePerkyFellowThePerkyFellow
Timeline (top)
commented ×3subscribed ×1

Error Message

The Linkedin native node doesn't seem to work any more. Here's the error:

  • error: all

PR fix notes

PR #28564: fix(LinkedIn Node): Update LinkedIn API version in request headers

Description (problem / solution / changelog)

Summary

This PR fixes a breaking issue in the LinkedIn node where requests fail with:

Requested version 20250401 is not active

The failure is caused by using an outdated LinkedIn API version (202504), which is no longer supported.

What was happening

  • LinkedIn deprecated the API version 202504
  • The n8n LinkedIn node was still sending requests using this version
  • This resulted in all requests failing with HTTP 426 (NONEXISTENT_VERSION)
  • As a result, workflows using the LinkedIn node stopped working entirely

What has changed

  • Updated the LinkedIn API version from 202504 → 202604
  • Restored compatibility with the currently active LinkedIn API version
  • No breaking changes to existing workflows

How to test

  1. Use a workflow with the LinkedIn node (Post → Create)
  2. Run the workflow before applying this fix → observe failure with version error
  3. Apply this fix
  4. Run the workflow again → confirm successful post creation

Related Linear tickets, Github issues, and Community forum posts

fixes #28559

Review / Merge checklist

  • I have seen this code, I have run this code, and I take responsibility for this code.
  • PR title and summary are descriptive.
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR labeled appropriately if backport is required

Changed files

  • packages/nodes-base/nodes/LinkedIn/GenericFunctions.ts (modified, +1/-1)
RAW_BUFFERClick to expand / collapse

Bug Description

The Linkedin native node doesn't seem to work any more. Here's the error:

"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": "LinkedIn Publish", "nodeType": "n8n-nodes-base.linkedIn", "nodeVersion": 1, "resource": "post", "operation": "create", "time": "16/4/2026, 10:01:25 am", "n8nVersion": "2.15.0 (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_@[email protected]_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_@[email protected]_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_@[email protected]_@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_@[email protected]_@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_@[email protected]_@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_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2315:11" ] } }

To Reproduce

Try posting anything using the native LinkedIn node.

Expected behavior

This was working until yesterday! All of my workflow has stopped working

Debug Info

Debug info

core

  • n8nVersion: 2.16.1
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: 864bb369-71cb-4208-9171-9151c3650a4f

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36 edg/147.0.0.0
  • isTouchDevice: false

Generated at: 2026-04-16T03:39:27.047Z

Operating System

Hostinger VPS

n8n Version

2.16.1

Node.js Version

n/A

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

The LinkedIn native node issue can likely be resolved by updating the API version being requested, as the current version 20250401 is not active.

Guidance

  • Verify the current LinkedIn API version being used in the n8n workflow and check if it matches the version specified in the error message (20250401).
  • Check the LinkedIn API documentation to determine the latest active version and update the n8n workflow accordingly.
  • If updating the API version is not feasible, consider reaching out to LinkedIn support to inquire about the deprecation of version 20250401 and potential alternatives.
  • Review the n8n workflow configuration to ensure it is compatible with the updated API version.

Example

No code snippet is provided as the issue is related to API versioning and configuration.

Notes

The issue seems to be related to a change in the LinkedIn API, and updating the API version in the n8n workflow should resolve the issue. However, it is essential to verify the compatibility of the updated API version with the n8n workflow configuration.

Recommendation

Apply workaround: Update the LinkedIn API version in the n8n workflow to the latest active version, as the current version 20250401 is not active. This should resolve the issue and allow the workflow to function as expected.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

This was working until yesterday! All of my workflow has stopped working

#api#configuration error#environment variable#network issue#logging issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING