npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-crawlora

v0.3.1

Published

n8n community node for Crawlora — structured web data from the public web.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

tonywangiotonywangio

Keywords

n8n-community-node-packagen8ncrawloraweb-scrapingweb-dataapi

Readme

n8n-nodes-crawlora

An n8n community node for Crawlora — get structured web data from the public web (search, maps, e‑commerce, social, finance, page content, and more) without maintaining your own parsers.

This node exposes the Crawlora API as n8n Resources, each with Operations (the endpoints under it):

  • Web scraping — URL → Markdown / HTML / links / metadata, contact extraction, anti‑bot check
  • Search — Google, Bing, Brave (web, news, images, videos, suggest) plus Google Maps, Jobs, Trends
  • Finance — Yahoo Finance and Google Finance (quotes, financials, news, history)
  • E‑commerce — Amazon, eBay, Shopify, Shop.app
  • Social — YouTube, Reddit, TikTok, Instagram, LinkedIn
  • App stores — Apple App Store, Google Play
  • Reviews & entertainment — Trustpilot, IMDb, Rotten Tomatoes, Spotify
  • Real estate & places — Zillow, Maps business datasets, geocoding

It ships a curated set of the most-used sources — more are added by demand. Properties are generated from the Crawlora OpenAPI spec, so they stay in sync with the API.

Installation

In n8n: Settings → Community Nodes → Install, then enter n8n-nodes-crawlora.

(Self-hosted manual install and local development are covered under "Development" below.)

Credentials

Create a Crawlora API credential and paste your API key. It is sent as the x-api-key header on every request. Get a key from your Crawlora dashboard — new accounts include a free monthly credit allowance, no card required.

Usage

  1. Add the Crawlora node to a workflow.
  2. Pick a Resource (the data source) and an Operation (the endpoint).
  3. Fill in the fields and run.

The node is also usable as a tool inside the n8n AI Agent, so an agent can call Crawlora operations directly.

Prefer MCP? Crawlora also ships a hosted MCP server with the full catalog — use n8n's MCP Client node to call every Crawlora tool from an AI Agent workflow. See https://docs.crawlora.net.

Development

The node's properties are generated at build time from the Crawlora OpenAPI spec and committed as nodes/Crawlora/properties.json, so the published package has no runtime dependencies.

npm install
SWAGGER_PATH=<file-or-url> npm run gen   # regenerate properties.json from the Crawlora API spec
npm run build                            # tsc + copy assets into dist/
npm run smoke                            # load the built node and print resource/operation counts

npm run gen loads the Crawlora OpenAPI/Swagger spec from SWAGGER_PATH (a file path or URL), converts it to OpenAPI 3.0, drops internal/account endpoints, and rebuilds the node properties.

Publishing

CI builds and smoke-tests on every push/PR. To release, push a v* tag — the Publish workflow publishes to npm with provenance (required for n8n community-node verification since 2026-05-01):

npm version <patch|minor>   # creates the v* tag
git push --follow-tags

One-time: add an automation npm token as the NPM_TOKEN repository secret. Lint the package against n8n's guidelines with npx @n8n/scan-community-package ., then submit it for the verified badge per the n8n community-node docs.

Links

  • API documentation: https://docs.crawlora.net
  • Crawlora: https://crawlora.net

License

MIT