# ScrapeGraphAI integrations: scraping and crawls

> Start a crawl and create a monitor in ScrapeGraphAI, and start a workflow when ScrapeGraphAI sends “Monitor check completed”.

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

## Overview

ScrapeGraphAI is a web data extraction service that uses AI to scrape pages, pull structured data from them, search the web, crawl sites and watch pages for changes. Tray.ai connects to ScrapeGraphAI through the HTTP Connector, so your workflows can call the ScrapeGraphAI API alongside the rest of your stack.

## Use cases

### Scraping

Read and manage scraping in ScrapeGraphAI from any Tray.ai workflow. The ScrapeGraphAI API covers calls such as scrape a page and extract structured data.

- Scrape a page
- Extract structured data
- Search the web

### Crawls

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

- Start a crawl
- Get crawl status
- Get crawl pages

### Monitors

Read, create, update, and delete monitors in ScrapeGraphAI from any Tray.ai workflow. The ScrapeGraphAI API covers calls such as create a monitor and list monitors.

- Create a monitor
- List monitors
- Update a monitor

### Account

Read account in ScrapeGraphAI from any Tray.ai workflow. The ScrapeGraphAI API covers calls such as get request history and get remaining credits.

- Get request history
- Get remaining credits

## Challenges Tray.ai solves

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

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

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

The ScrapeGraphAI API uses 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 ScrapeGraphAI connector?

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