# Scrapfly integrations: scraping and crawls

> Run a batch of scrapes and start a crawl in Scrapfly, and start a workflow when Scrapfly sends “Crawler started”.

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

## Overview

Scrapfly is a web scraping platform with APIs for fetching pages through managed proxies and browsers, taking screenshots, extracting structured data and crawling whole sites. Tray.ai connects to Scrapfly through the HTTP Connector, so your workflows can call the Scrapfly API alongside the rest of your stack.

## Use cases

### Scraping

Create and manage scraping in Scrapfly from any Tray.ai workflow. The Scrapfly API covers calls such as scrape a web page and run a batch of scrapes.

- Scrape a web page
- Run a batch of scrapes
- Capture a page screenshot

### Crawls

Read, create, and delete crawls in Scrapfly from any Tray.ai workflow. The Scrapfly API covers calls such as start a crawl and get crawl status.

- Start a crawl
- Get crawl status
- List crawled URLs

### Extraction

Read extraction in Scrapfly from any Tray.ai workflow. The Scrapfly API covers calls such as extract data with a template and extract data with a prompt.

- Extract data with a template
- Extract data with a prompt
- Extract data with a model

### Scrapfly events

Start a Tray.ai workflow the moment something happens in Scrapfly. Scrapfly sends events such as crawler started and crawler finished to a Tray.ai webhook trigger.

- Crawler started
- Crawler finished
- Crawler cancelled

## Challenges Tray.ai solves

### Keeping Scrapfly 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 Scrapfly 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 Scrapfly 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 Scrapfly 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 Scrapfly?

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

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

The Scrapfly API uses an API key in the query string and an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Scrapfly connector?

Scrapfly runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Scrapfly connector from the Scrapfly 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/
