Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix LinkedIn node broken - API version 20250401 is not active [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#28600•Fetched 2026-04-18 05:57:22
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
0
Author
waqasamunawarwaqasamunawar
Participants
JoffcomJoffcomn8n-assistant[bot]n8n-assistant[bot]waqasamunawarwaqasamunawar
Timeline (top)
commented ×2closed ×1labeled ×1mentioned ×1

Error Message

Describe the problem/error/question

The built-in LinkedIn node (n8n-nodes-base.linkedIn) is calling a deprecated LinkedIn API version (20250401) which LinkedIn has sunset. All calls return error 426 NONEXISTENT_VERSION.

What is the error message (if any)?

  • error: all

Code Example

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

The built-in LinkedIn node (n8n-nodes-base.linkedIn) is calling a deprecated LinkedIn API version (20250401) which LinkedIn has sunset. All calls return error 426 NONEXISTENT_VERSION.

What is the error message (if any)?

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

Please share your workflow/screenshots/recording

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

  • n8nVersion: 2.17.2
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 5
  • license: enterprise (sandbox)

storage

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

pruning

  • enabled: true
  • maxAge: 168 hours
  • maxCount: 2500 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
  • isTouchDevice: false

Generated at: 2026-04-17T07:45:49.800Z

extent analysis

TL;DR

Update the LinkedIn node to use a supported API version to resolve the 426 NONEXISTENT_VERSION error.

Guidance

  • Verify the current LinkedIn API version being used by the n8n-nodes-base.linkedIn node and check the LinkedIn API documentation for the latest supported version.
  • Check if there are any updates available for the n8n-nodes-base.linkedIn node that support the latest LinkedIn API version.
  • If an update is not available, consider reaching out to the node maintainer or the n8n community for assistance in updating the node to use a supported API version.
  • Review the LinkedIn API deprecation policy to understand the timeline for sunsetting older API versions and plan accordingly.

Example

No code snippet is provided as the issue is related to a specific node and API version, and without more information about the node's implementation, it's difficult to provide a concrete example.

Notes

The solution may require updating the n8n-nodes-base.linkedIn node or modifying the workflow to use a different node that supports the latest LinkedIn API version. Additionally, the LinkedIn API version used by the node may need to be updated manually if an automated update is not available.

Recommendation

Apply workaround: Update the LinkedIn node to use a supported API version, as the current version (20250401) has been sunset by LinkedIn.

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…
#api#chain error#conversation history#tool integration#LLM response

Still need to ship something?

×6

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

Back to top recommendations

TRENDING