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

@crawlbase/n8n-nodes-crawlbase

v1.2.2

Published

Crawlbase node for n8n — crawl web pages, scrape public information, bypass CAPTCHAs, run automations

Readme

n8n-nodes-crawlbase

Crawlbase node for n8n. Crawl web pages with native Crawlbase API credentials and the Crawling API — no need to wire a generic HTTP Request node by hand.

Features

  • Native credentials — Add your Crawlbase API token once and use it across workflows; Test connection validates the token.
  • Crawling API — Single node for GET/POST/PUT with URL (from parameter or from each input item).
  • Options — Optional Crawling API parameters (for example format, page_wait, country, request_headers, cookies, device, scraper, screenshot, store, async, and JS rendering helpers), request body for POST/PUT, and an HTTP timeout on the client (not a Crawlbase query parameter). See Crawling API parameters for the full list and behavior.
  • Normalized output — Each item returns statusCode, headers, body, and metadata (including originalStatus, cbStatus, url where provided by the API).

Installation

In n8n (Community nodes)

  1. In n8n, go to SettingsCommunity nodesInstall a community node.
  2. Enter: n8n-nodes-crawlbase.
  3. Install and restart if prompted.

From source

npm install
npm run build

Then in n8n, add the path to this package (the directory containing this README) as a community node in SettingsCommunity nodes, or use npm run dev to run n8n with this node loaded locally.

Credentials

  1. Add a Crawlbase API credential (search for “Crawlbase” in the credential list).
  2. Enter your API Token from the Crawlbase dashboard.
  3. Click Test connection to confirm the token works.

First crawl

  1. Add a Crawlbase node to your workflow.
  2. Select your Crawlbase API credential.
  3. Enter a URL (e.g. https://example.com) or choose From input item field and set the field name.
  4. Choose Method (GET/POST/PUT) and Response format (HTML, JSON, or Markdown).
  5. Run the workflow. The node outputs statusCode, headers, body, and metadata for each URL.

Item-list mode

  • Set URL Source to From input item field and specify the field that contains the URL (e.g. url).
  • Connect an input that provides one item per URL. The node runs one Crawling API request per item and returns one output item per input item.

Rate limits and retries

Crawlbase applies rate limits depending on your plan. To avoid failures:

  • Use n8n’s Retry On Fail on the Crawlbase node (node settings).
  • Set Wait Between Tries to at least 1 second (or higher if you hit limits).
  • For many URLs, consider splitting work (e.g. Loop Over Items / batching) so you don’t send bursts of requests.

Example workflow

See example-workflow.json for a workflow that crawls a single public URL and returns HTML. Import it in n8n via WorkflowsImport from file.

Links

License

MIT


Copyright 2026 Crawlbase