# ParseHub integrations: projects and runs

> Run a project in ParseHub and start a workflow when ParseHub sends “Run status changed”.

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

## Overview

ParseHub is a visual web scraping tool that extracts data from websites into projects you can run on a schedule and download as JSON or CSV. Tray.ai connects to ParseHub through the HTTP Connector, so your workflows can call the ParseHub API alongside the rest of your stack.

## Use cases

### Projects

Read projects in ParseHub from any Tray.ai workflow. The ParseHub API covers calls such as list projects and get a project.

- List projects
- Get a project
- Run a project

### Runs

Read and delete runs in ParseHub from any Tray.ai workflow. The ParseHub API covers calls such as get a run and get run data.

- Get a run
- Get run data
- Cancel a run

### ParseHub events

Start a Tray.ai workflow the moment something happens in ParseHub. ParseHub sends events such as run status changed and run data ready to a Tray.ai webhook trigger.

- Run status changed
- Run data ready

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated ParseHub connector?

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