n8n - 💡(How to fix) Fix Hi n8n team, Details: Node type: n8n-nodes-base.linkedIn [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#29356Fetched 2026-04-29 06:35:18
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
0
Author
Timeline (top)
commented ×2closed ×1labeled ×1mentioned ×1

Error Message

Error response:

Fix Action

Fix / Workaround

Could you please update or patch the LinkedIn node for my Cloud instance?

RAW_BUFFERClick to expand / collapse

Hi n8n team,

My LinkedIn node is failing on n8n Cloud.

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

Details: Node type: n8n-nodes-base.linkedIn n8n Cloud version: 1.123.16 LinkedIn node version: 1 latest

It looks like the LinkedIn node is still sending an inactive LinkedIn-Version header: 20250401.

Could you please update or patch the LinkedIn node for my Cloud instance?

Thank you.

extent analysis

TL;DR

The LinkedIn node needs to be updated to use an active LinkedIn API version.

Guidance

  • Verify the current LinkedIn API versions and identify an active version to use.
  • Check the n8n Cloud documentation for any available updates or patches for the LinkedIn node.
  • Consider reaching out to the n8n team for assistance with updating the LinkedIn node for your Cloud instance.
  • Review the LinkedIn node configuration to ensure it is set to use the latest version.

Example

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

Notes

The issue seems to be specific to the n8n Cloud environment and the LinkedIn node, so the solution may not apply to other environments or nodes.

Recommendation

Apply workaround: Update the LinkedIn node to use an active API version, as the current version (20250401) is inactive.

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…

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 Hi n8n team, Details: Node type: n8n-nodes-base.linkedIn [2 comments, 3 participants]