n8n has no built-in Firecrawl node: n8n’s integrations documentation lists none. To scrape, crawl or map websites with Firecrawl from a workflow, you install a community node or call Firecrawl’s API yourself with the built-in HTTP Request node. The most used option is the official package from the Firecrawl team. This guide compares the Firecrawl community packages using the description and README each author publishes on npm and our own download data.
Firecrawl community nodes
Our Firecrawl hub lists 6 packages that pass our quality rule. Weekly npm downloads as of 27 October 2026:
| Package | Weekly downloads | Latest version | Author’s description |
|---|---|---|---|
| @mendable/n8n-nodes-firecrawl | 79,728 | 2.2.0 (18 September 2026) | Official Firecrawl nodes: scrape, crawl, map, search and extract data from websites, with AI Agent tool usage |
| n8n-nodes-firecrawl | 674 | 0.3.0 (3 October 2024) | FireCrawl nodes for n8n |
| n8n-nodes-firecrawl-v1 | 74 | 0.4.21 (26 January 2025) | FireCrawl nodes for n8n |
| n8n-nodes-firecrawl-v2 | 26 | 2.0.1 (11 September 2026) | Firecrawl v2 API, Cloud and self-hosted: scrape, crawl, map, search, extract and batch operations |
| n8n-nodes-firecrawl-scraper | 19 | 1.1.7 (6 March 2025) | A custom n8n node based on Firecrawl |
| n8n-nodes-firecrawl-tool | 4 | 0.1.2 (28 August 2025) | Firecrawl v2 API for workflows and AI agents |
Versions and dates come from the npm registry.
@mendable/n8n-nodes-firecrawl (official)
Its repository is in the firecrawl GitHub organization and its npm description calls it the official Firecrawl node. The README lists these operations:
- Scrape: one URL to LLM-ready content (markdown, structured data through LLM Extract, screenshot, HTML).
- Crawl: every URL of a site, plus Get Crawl Status, Get Crawl Errors, Cancel Crawl, Crawl Active and Crawl Params Preview (crawl settings generated from a plain-language prompt).
- Map: all the URLs of a website.
- Search: a web search, optionally scraping the results.
- Batch Scrape: many URLs in one job, with Batch Scrape Status and Batch Scrape Errors.
- Extract Data: structured data from one page, several pages or a whole site, with Get Extract Status.
- Usage: Team Token Usage, Team Credit Usage, Historical Credit Usage, Historical Token Usage and Team Queue Status.
You authenticate with an API key from your Firecrawl dashboard. The node also works as a tool for n8n’s AI Agent node. Its README says this needs n8n 1.79.0 or newer and the environment variable N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true, and that you can let the agent fill fields such as the URL with $fromAI().
n8n-nodes-firecrawl and n8n-nodes-firecrawl-v1
Both come from the same author and repository and share one README, which lists Scrape, Crawl and Map. Their last releases date from October 2024 and January 2025.
n8n-nodes-firecrawl-v2
Targets Firecrawl’s v2 API and works with Firecrawl Cloud or a self-hosted Firecrawl: the credential has a Base URL (default https://api.firecrawl.dev/v2, which must include /v2) and an API key. Its README lists scrape, crawl, map, search, extract and batch operations and says it requires self-hosted n8n, because it is not a verified node.
n8n-nodes-firecrawl-tool
Also built for the v2 API, as a normal workflow node and as an AI tool for n8n’s AI Agent and MCP Trigger nodes. Its README lists Scrape, Crawl, Map, Search and Extract, plus caching and page actions such as clicks and scrolls before scraping. The credential takes an API key and an optional API host for a self-hosted Firecrawl.
n8n-nodes-firecrawl-scraper
A wrapper around Firecrawl’s npm SDK, focused on the extract feature: one Firecrawl node with Scrape, Crawl, Map and Extract (simple or schema-based). Its README says the project is still in development.
Check each node page here for the latest release and, where it has one, its GitHub repository for open issues before you build on a package.
How to choose
- Most workflows: the official @mendable/n8n-nodes-firecrawl. It has the longest operation list, is maintained by the Firecrawl team and is by far the most installed.
- A self-hosted Firecrawl server: n8n-nodes-firecrawl-v2 or n8n-nodes-firecrawl-tool, whose credentials take your own base URL or host.
- An AI agent that browses the web: the official node or n8n-nodes-firecrawl-tool, both usable as AI Agent tools.
- Full control over the request: the HTTP Request node with Firecrawl’s API documentation.
To install a package on a self-hosted instance, an owner or admin enters its npm name in Settings > Community Nodes; full steps are in How to Install n8n Community Nodes. On n8n Cloud only verified community nodes can be installed, see Verified vs Unverified n8n Community Nodes. For the tool-usage variable, see n8n Community Node Environment Variables.
FAQ
Does n8n have a Firecrawl node?
Not a built-in one. The official Firecrawl node, @mendable/n8n-nodes-firecrawl, is a community node published by the Firecrawl team.
Can an n8n AI agent use Firecrawl?
Yes. The official node’s README says it works as an AI Agent tool on n8n 1.79.0 or newer with N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true. n8n-nodes-firecrawl-tool is also built for AI agent use.
Can I use a self-hosted Firecrawl with n8n?
n8n-nodes-firecrawl-v2 and n8n-nodes-firecrawl-tool let you change the API base URL or host to your own Firecrawl instance.
What is the most used Firecrawl community node?
@mendable/n8n-nodes-firecrawl, with 79,728 weekly npm downloads on 27 October 2026.
