n8n - 💡(How to fix) Fix linkedin post [3 comments, 4 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#28590Fetched 2026-04-17 08:54:46
View on GitHub
Comments
3
Participants
4
Timeline
9
Reactions
0
Author
Timeline (top)
commented ×3closed ×1cross-referenced ×1labeled ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

Error details Error code

  • 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

What is the error message (if any)?

im getting this when i try to post to linkedin on the api node for linkedin Your request is invalid or could not be processed by the service Requested version 20250401 is not active

n8n AI Error details

From LinkedIn Error code

426

Full message

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

n8n-nodes-base.linkedIn

Node version

1 (Latest)

n8n version

2.17.2 (Cloud)

Time

4/16/2026, 6:51:39 PM

Stack trace

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:104: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:1048:9) 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:1239: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:1687: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:2339:11

think you need to update your linkedin node or is this me

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 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/145.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-16T17:51:53.404Z

extent analysis

TL;DR

The issue is likely due to an inactive LinkedIn API version being requested, and updating the LinkedIn node or changing the API version might resolve the problem.

Guidance

  • Check the LinkedIn API documentation to see if version 20250401 is indeed inactive or deprecated.
  • Verify if there are any updates available for the n8n-nodes-base.linkedIn node, as the error message suggests updating the node.
  • Consider changing the API version in the node settings to a currently active version, if possible.
  • Review the workflow and node configuration to ensure that the correct API version is being requested.

Example

No code example is provided as the issue seems to be related to configuration or versioning rather than code.

Notes

The solution might depend on the specific requirements of the workflow and the LinkedIn API. It's essential to check the LinkedIn API documentation and the n8n-nodes-base.linkedIn node documentation for more information on available API versions and node configuration.

Recommendation

Apply workaround: Update the LinkedIn node or change the API version to a currently active one, as the error message suggests that the requested version is not active.

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