chore: Update node popularity data#16
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
f52e62d to
b57e4bf
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
b57e4bf to
5a0c103
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
5a0c103 to
38a269f
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
38a269f to
6ad3c37
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
6ad3c37 to
37414b0
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
2 times, most recently
from
e209e19 to
b94fd89
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
b94fd89 to
ffa0d73
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
ffa0d73 to
19f7417
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This automated PR updates the node popularity data used for sorting nodes in the node creator panel.
The data is fetched weekly from the n8n telemetry endpoint to reflect current usage patterns.
Generated by the weekly node popularity update workflow.
Note
Low Risk
Data-only refresh for UI sorting; no runtime or security behavior changes beyond which nodes rank higher in the picker.
Overview
Refreshes
packages/frontend/editor-ui/data/node-popularity.jsonwith the latest telemetry-derived popularity scores and sort order used when searching and listing nodes in the node creator (useViewStacks/searchNodes).The file is fully reordered: entries at the top now reflect current usage (e.g. LangChain agent, HTTP Request, OpenRouter) instead of the previous leading nodes (webhook, scheduleTrigger, set). Many community and newer node types are included with updated scores; nodes missing from telemetry may appear with 0 popularity.
No application logic changes—only the cached dataset consumed by the weekly popularity workflow.
Reviewed by Cursor Bugbot for commit 19f7417. Bugbot is set up for automated code reviews on this repo. Configure here.