n8n - 💡(How to fix) Fix LinkedIn node sends deprecated LinkedIn-Version 20250401 → 426 NONEXISTENT_VERSION [2 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#28660Fetched 2026-04-20 12:15:14
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
0
Author
Timeline (top)
commented ×2mentioned ×2subscribed ×2closed ×1

Error Message

Error returned by LinkedIn:

Root Cause

The LinkedIn node (n8n-nodes-base.linkedIn) fails on every Post Create request with HTTP 426 because it sends a deprecated LinkedIn-Version header.

RAW_BUFFERClick to expand / collapse

Bug Description

The LinkedIn node (n8n-nodes-base.linkedIn) fails on every Post Create request with HTTP 426 because it sends a deprecated LinkedIn-Version header.

Error returned by LinkedIn:

{ "status": 426, "code": "NONEXISTENT_VERSION", "message": "Requested version 20250401 is not active" }

The version 20250401 is hardcoded in packages/nodes-base/nodes/LinkedIn/GenericFunctions.ts around line 71. LinkedIn keeps monthly API versions active for roughly 12 months, so April 2025 has now been retired and every LinkedIn Post node in n8n currently fails.

To Reproduce

  1. Create a workflow with a LinkedIn node (Resource: Post, Operation: Create)
  2. Authenticate with valid LinkedIn OAuth2 credentials (scope w_member_social)
  3. Execute the node with any valid text payload
  4. The node fails with 426 NONEXISTENT_VERSION

Expected behavior

The node should send a currently supported LinkedIn-Version header (e.g. 202508 or later). A maintenance bump of this constant, and ideally making it configurable or auto-incrementing, would prevent the node from silently breaking every ~12 months when LinkedIn retires old versions.

Debug Info

n8n 2.16.1
OS darwin arm64 (o linux x64 del VPS)
Node vXX.XX.X
Database sqlite/postgres
Execution mode regular

Operating System

Ubuntu 24

n8n Version

2.16.1

Node.js Version

v24.14.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

extent analysis

TL;DR

Update the hardcoded LinkedIn-Version header in GenericFunctions.ts to a currently supported version, such as 202508 or later, to resolve the HTTP 426 error.

Guidance

  • Identify the current supported LinkedIn API versions and update the hardcoded 20250401 value in packages/nodes-base/nodes/LinkedIn/GenericFunctions.ts to the latest version.
  • Consider making the LinkedIn-Version header configurable or auto-incrementing to prevent future breakages when LinkedIn retires old versions.
  • Verify the fix by executing the LinkedIn node with a valid text payload and checking for a successful response.
  • Review LinkedIn's API documentation to ensure compliance with their versioning policy and to stay up-to-date with the latest supported versions.

Example

// packages/nodes-base/nodes/LinkedIn/GenericFunctions.ts
// Update the hardcoded version to a currently supported version
const linkedInVersion = '202508'; // or later

Notes

The provided solution assumes that updating the hardcoded version will resolve the issue. However, it is recommended to consult LinkedIn's API documentation to ensure compliance with their versioning policy and to stay up-to-date with the latest supported versions.

Recommendation

Apply workaround: Update the hardcoded LinkedIn-Version header to a currently supported version, as this will resolve the immediate issue and allow the LinkedIn node to function correctly. A more permanent solution would involve making the version configurable or auto-incrementing, but this may require additional development and testing.

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

The node should send a currently supported LinkedIn-Version header (e.g. 202508 or later). A maintenance bump of this constant, and ideally making it configurable or auto-incrementing, would prevent the node from silently breaking every ~12 months when LinkedIn retires old versions.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix LinkedIn node sends deprecated LinkedIn-Version 20250401 → 426 NONEXISTENT_VERSION [2 comments, 3 participants]