# Firecrawl AI integration on Definable

> Firecrawl automates web crawling and data extraction, enabling organizations to gather content, index sites, and gain insights from online sources at scale

## What this connects

Firecrawl automates web crawling and data extraction, enabling organizations to gather content, index sites, and gain insights from online sources at scale

Vendor: https://www.firecrawl.dev/

## Tools available

**30** tools available. First 12:

- `FIRECRAWL_AGENT_CANCEL` — Cancel an agent job — Tool to cancel an in-progress agent job by its ID. Use when you need to terminate an active agent operation. The API returns a success boolean upon cancellation.
- `FIRECRAWL_BATCH_SCRAPE` — Batch scrape multiple URLs — Tool to scrape multiple URLs in batch with concurrent processing. Use when you need to scrape multiple web pages efficiently with customizable formats and content filtering.
- `FIRECRAWL_BATCH_SCRAPE_CANCEL` — Cancel a batch scrape job — Tool to cancel a running batch scrape job using its unique identifier. Use when you need to terminate an in-progress batch scrape operation.
- `FIRECRAWL_BATCH_SCRAPE_GET` — Get batch scrape status — Retrieves the current status and results of a batch scrape job using the job ID. Use this to check batch scrape progress and retrieve scraped data.
- `FIRECRAWL_BATCH_SCRAPE_GET_ERRORS` — Get errors from batch scrape job — Tool to retrieve error details from a batch scrape job, including failed URLs and URLs blocked by robots.txt. Use when you need to debug or understand why certain pages failed to scrape in a batch operation.
- `FIRECRAWL_CRAWL` — Start a web crawl — Initiates a Firecrawl web crawl from a given URL, applying various filtering and content extraction rules, and polls until the job is complete; ensure the URL is accessible and any regex patterns for paths are valid.
- `FIRECRAWL_CRAWL_CANCEL` — Cancel a crawl job — Cancels an active or queued web crawl job using its ID; attempting to cancel completed, failed, or previously canceled jobs will not change their state.
- `FIRECRAWL_CRAWL_DELETE` — Cancel a crawl job — Tool to cancel a running crawl job by its ID. Use when you need to stop an active crawl operation. The API returns a status of 'cancelled' upon successful cancellation.
- `FIRECRAWL_CRAWL_GET` — Get crawl job status — Tool to retrieve the status and results of a Firecrawl crawl job. Use when you need to check the progress or get data from an ongoing or completed crawl operation. Returns crawl status, progress metrics, credits used, and the crawled page data.
- `FIRECRAWL_CRAWL_GET_ERRORS` — Get errors from a crawl job — Tool to retrieve errors from a Firecrawl crawl job. Use when you need to understand why certain pages failed to scrape or which URLs were blocked by robots.txt during a crawl operation.
- `FIRECRAWL_CRAWL_LIST_ACTIVE` — Get all active crawl jobs — Tool to retrieve all active crawl jobs for the authenticated team. Use when you need to see which crawl operations are currently running.
- `FIRECRAWL_CRAWL_PARAMS_PREVIEW` — Preview crawl parameters — Preview crawl parameters before starting a crawl by generating optimal configuration from natural language instructions. Use this tool to understand what crawl settings will be applied based on your requirements before executing a full crawl operation. The endpoint intelligently interprets natural language prompts to configure crawl parameters like include/exclude paths, depth limits, and domain scope.

## Auth

Auth schemes: `API_KEY`.

## How agents use Firecrawl

Inside a Definable workflow, Firecrawl is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Firecrawl** — the Researcher (GPT-5.5) pulls context from Firecrawl (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Firecrawl** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Firecrawl (create record, post message, draft email).
- **Designer / Engineer → Distributor → Firecrawl** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Firecrawl (attach file, open PR comment, post status).

The Verifier checks every Firecrawl call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- ai web scraping — https://definable.ai/apps/category/ai-web-scraping/
- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/firecrawl/
- Same category (ai web scraping): https://definable.ai/apps/category/ai-web-scraping/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt