n8n - 💡(How to fix) Fix Wrong version of community node [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#29202Fetched 2026-04-28 06:49:26
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
0
Timeline (top)
commented ×2mentioned ×2subscribed ×2closed ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

No error message

  • 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

N8N is showing me that I'm on the latest version of a community node (1.2), but the actualy last version is another one (1.4)

What is the error message (if any)?

No error message

<img width="1192" height="209" alt="Image" src="https://github.com/user-attachments/assets/4524ea68-3065-49e4-8553-9dd116fdc360" />

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: 1.123.33
  • platform: docker (cloud)
  • nodeJsVersion: 24.13.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/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-27T09:39:01.888Z}

extent analysis

TL;DR

The community node version in N8N may not be updating correctly, causing a discrepancy between the displayed version and the actual latest version.

Guidance

  • Check the node's update mechanism to ensure it is properly configured to fetch the latest version.
  • Verify the version number in the node's configuration or settings to confirm the mismatch.
  • Consider manually updating the node to the latest version (1.4) if possible.
  • Review the N8N documentation for any specific instructions on updating community nodes.

Notes

The issue may be related to the node's update mechanism or N8N's version management. Without more information, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Manually update the community node to the latest version (1.4) if possible, as the automatic update mechanism appears to be faulty.

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