n8n Node Catalog & Community Package Scraper
Pricing
from $4.50 / 1,000 n8n nodes founds
Extract every n8n node into one dataset - built-in, verified, and community. Get node types, type versions, operations, and credential requirements, plus npm provenance, license, weekly downloads, and maintenance risk, so you can tell a safe n8n integration from an abandoned one.
builtin = the ~527 nodes shipped with n8n. verified = the ~1,490 nodes n8n has verified across ~1,175 packages. community = every n8n node package on npm, around 13,500. Adding community turns a run from seconds into minutes. Ignored when Package names is set.
[ "builtin"]Catalog only these npm packages, for example @apify/n8n-nodes-apify. These are npm package names, not node types like n8n-nodes-base.httpRequest. Overrides Sources, skips npm discovery, and enriches every package from its tarball. Leave empty to catalog the selected sources in full.
[]Include built-in nodes n8n marks as hidden. Adds ~45 rows.
How much of the npm long tail to reach. full scans every package name in the npm registry - the most complete option, and the recommended one. balanced reaches the tail through keyword partitioning alone. searchWindow stops at npm's first ~5,000 results.
Catalog at most this many packages in total, across every source. 0 means no limit. The budget is spent in source order - built-in, then verified, then npm - so set Sources to community alone to spend it on npm packages.
Recover exact node types, display names, type versions, and credential types. Slower and heavier, so it is off by default. Lookup mode enriches regardless of this setting.
Enables star counts and last-commit dates for unverified packages. That step is skipped when no token is set.
On by default, and used only for npm's rate-limited search and download-count endpoints. Pick the RESIDENTIAL group for a full community catalogue. Turn it off for a direct connection - a full run still completes, but its long-tail download counts may come back empty.
{ "useApifyProxy": true}