# Firecrawl integrations: scrape, crawl and map

> Start a crawl in Firecrawl and start a workflow when Firecrawl sends “Crawl started”.

**Canonical page:** https://tray.ai/connectors/firecrawl-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Firecrawl is a web scraping API that turns websites into clean markdown or structured data for AI applications, with crawling, mapping and search. Tray.ai connects to Firecrawl through the HTTP Connector, so your workflows can call the Firecrawl API alongside the rest of your stack.

## Use cases

### Scrape

Work with scrape in Firecrawl from any Tray.ai workflow. The Firecrawl API covers calls such as scrape a page and batch scrape pages.

- Scrape a page
- Batch scrape pages

### Crawl

Read and create crawl in Firecrawl from any Tray.ai workflow. The Firecrawl API covers calls such as start a crawl and get crawl results.

- Start a crawl
- Get crawl results

### Map

Read map in Firecrawl from any Tray.ai workflow. The Firecrawl API covers calls such as map a website and list site URLs.

- Map a website
- List site URLs

### Search

Read search in Firecrawl from any Tray.ai workflow. The Firecrawl API covers calls such as search the web and return page content.

- Search the web
- Return page content

### Extract

Read extract in Firecrawl from any Tray.ai workflow. The Firecrawl API covers calls such as extract structured data and get extraction results.

- Extract structured data
- Get extraction results

### Firecrawl events

Start a Tray.ai workflow the moment something happens in Firecrawl. Firecrawl sends events such as crawl started and page crawled to a Tray.ai webhook trigger.

- Crawl started
- Page crawled
- Crawl completed

## Challenges Tray.ai solves

### Keeping Firecrawl credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Firecrawl credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Firecrawl API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Firecrawl API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Firecrawl?

Yes. Tray.ai connects to Firecrawl through the HTTP Connector, which calls the Firecrawl API directly. Any call the Firecrawl API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Firecrawl?

The Firecrawl API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Firecrawl connector?

Firecrawl runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Firecrawl connector from the Firecrawl API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/